← Back
CVE-2025-68131
Vulnerability in cbor2 (CVE-2025-68131)
Summary
vulnerability in cbor2 (CVE-2025-68131). Confidential information can be exposed externally. Mitigation: upgrade to `5.8.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2025-68131** has been found in cbor2.
Confidential information can be exposed externally. CVSS score: ?/10.
What to do: upgrade cbor2 to **5.8.0** or later.
If unsure, ask your IT team or search "cbor2 CVE-2025-68131" on the vendor's site.
CVE-2025-68131 (cbor2) — CWE-212 /
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: `5.8.0` — apply immediately
Workaround: set flag: True
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-212) exists in cbor2.
📍 Affected scope
cbor2 — .
🔥 Severity
Severity: ?. Confidential information can be exposed externally
🔧 How to fix
Update to **5.8.0**.
🛡️ Workaround
Workaround: set flag: True
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'cbor2' .` 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 'cbor2' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `cbor2` を grep し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
set flag: Trueパッチが適用されるまでの応急処置として、set flag: True を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade cbor2 to 5.8.0ステージング環境で 5.8.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
cbor2
[{"type":"ECOSYSTEM","events":[{"introduced":"3.0.0"},{"fixed":"5.8.0"}]}]
pip
cbor2
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.8.0"}]}]
References
- advisory https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/68xxx/CVE-2025-68131.json
- advisory https://nvd.nist.gov/vuln/detail/CVE-2025-68131
- package https://github.com/agronholm/cbor2
- web https://github.com/agronholm/cbor2/security/advisories/GHSA-wcj4-jw5j-44wh
- web https://github.com/agronholm/cbor2/pull/268
- web https://github.com/agronholm/cbor2/commit/f1d701cd2c411ee40bb1fe383afe7f365f35abf0
- web https://github.com/pypa/advisory-database/tree/main/vulns/cbor2/PYSEC-2025-90.yaml
- web https://github.com/advisories/GHSA-wcj4-jw5j-44wh