← Back
CVE-2025-47285
Vulnerability in vyper (CVE-2025-47285)
Summary
vulnerability in vyper (CVE-2025-47285). Risk of unauthorized operations or information disclosure.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2025-47285** has been found in vyper.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "vyper CVE-2025-47285" on the vendor's site.
CVE-2025-47285 (vyper) — CWE-691 /
Workaround: don't have side effects in expressions which construct zero-length bytestrings.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (CWE-691) exists in vyper.
📍 Affected scope
vyper — .
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to the patched release per vendor advisory.
🛡️ Workaround
Workaround: don't have side effects in expressions which construct zero-length bytestrings.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'vyper' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'vyper' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `vyper` を grep し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
don't have side effects in expressions which construct zero-length bytestrings.パッチが適用されるまでの応急処置として、don't have side effects in expressions which construct zero-length bytestrings. を実施。回避策の副作用 (機能低下) を確認した上で。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
vyper
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"0.4.2rc1"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2025-47285
- advisory https://github.com/advisories/GHSA-qhr6-mgqr-mchm
- package https://github.com/vyperlang/vyper
- package https://pypi.org/project/vyper
- web https://github.com/vyperlang/vyper/security/advisories/GHSA-qhr6-mgqr-mchm
- web https://github.com/vyperlang/vyper/pull/4644
- web https://github.com/vyperlang/vyper/blob/68b68c4b30c5ef2f312b4674676170b8a6eaa316/vyper/builtins/functions.py#L560-L562