Vulnerability in resdata (CVE-2026-55209)
Summary
Vulnerability in resdata (CVE-2026-55209). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 6.2.9 or later.
Original description
The description as published by the source.
Impact
Prior to version 6.2.9 resdata would not correctly validate input in GRDECL files. The severity rating assumes that resdata is used to parse untrused files in a networking context such as a webservice.
Patches
The bug has been patched starting with version 6.2.9.
Source: GitHub Security Advisories (Global) 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-55209 has been found in resdata.
Successful exploitation can lead to full system takeover. CVSS score: 9.8/10.
What to do: upgrade resdata to 6.2.9 or later.
If unsure, ask your IT team or search "resdata CVE-2026-55209" on the vendor's site.
CVE-2026-55209 (resdata) — CWE-120 / CVSS v3 9.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 6.2.9 — 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-120) exists in resdata.
Check the vendor advisory for the affected versions of resdata.
Severity: Critical (CVSS 9.8/10). Successful exploitation can lead to full system takeover.
Update to 6.2.9.
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 'resdata' . 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 'resdata' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
resdataを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade resdata to 6.2.9ステージング環境で 6.2.9 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- package pypi.org
- web github.com
- web github.com
- web security-advisories@github.com
- web security-advisories@github.com
- web security-advisories@github.com
- web security-advisories@github.com