Vulnerability in devalue (CVE-2026-81176)
Summary
Vulnerability in devalue (CVE-2026-81176). Risk of unauthorized operations or information disclosure. Exploitable via devalue.parse. Mitigation: upgrade to 5.9.2 or later.
Original description
The description as published by the source.
Impact
devalue.parse prior to version 5.9.2 fails to reject out-of-bounds indices. Specially-crafted payloads can exploit this to cause devalue to alternate between different array representations, resulting in work that is quadratic with payload size.
Applications are potentially affected if they call devalue.parse with untrusted data.
Patches
The bug is fixed in devalue@5.9.2.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-81176 has been found in devalue.
Attackers can target a specific entry point like devalue.parse over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.3/10.
What to do: upgrade devalue to 5.9.2 or later.
If unsure, ask your IT team or search "devalue CVE-2026-81176" on the vendor's site.
CVE-2026-81176 (devalue) — CWE-770 / CVSS v3 5.3
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: devalue.parse
Patched: 5.9.2 — apply immediately
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.
A vulnerability (CWE-770) exists in devalue. Attackers reach the vulnerable code path via devalue.parse without authentication.
Check the vendor advisory for the affected versions of devalue. Attack surface: devalue.parse.
Severity: Medium (CVSS 5.3/10). Risk of unauthorized operations or information disclosure.
Update to 5.9.2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'devalue' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'devalue' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
devalueを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade devalue to 5.9.2ステージング環境で 5.9.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- web github.com
- web github.com
- web github.com
- web nvd.nist.gov
- web github.com