← Back
CVE-2026-42789
medium
CVSS 4.8
Vulnerability in erlang (CVE-2026-42789)
Summary
vulnerability in erlang (CVE-2026-42789). Risk of unauthorized operations or information disclosure.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-42789** has been found in erlang.
Risk of unauthorized operations or information disclosure. CVSS score: 4.8/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "erlang CVE-2026-42789" on the vendor's site.
CVE-2026-42789 (erlang) — CWE-295 / CVSS v3 4.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Workaround: The verify_fun option in the ssl or public_key application can be used to ensure that path validation rejects chains where an intermediate certificate does not have basicConstraints cA: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-295) exists in erlang.
📍 Affected scope
erlang — .
🔥 Severity
Severity: Medium (CVSS 4.8/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to the patched release per vendor advisory.
🛡️ Workaround
Workaround: The verify_fun option in the ssl or public_key application can be used to ensure that path validation rejects chains where an intermediate certificate does not have basicConstraints cA:true.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'erlang' .` 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 'erlang' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `erlang` を grep し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
The verify_fun option in the ssl or public_key application can be used to ensure that path validation rejects chains where an intermediate certificate does not have basicConstraints cA:true.パッチが適用されるまでの応急処置として、The verify_fun option in the ssl or public_key application can be used to ensure that path validation rejects chains where an intermediate certificate does not have basicConstraints cA:true. を実施。回避策の副作用 (機能低下) を確認した上で。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
References
- advisory 6b3ad84c-e1a6-4bf7-a703-f496b71e49db
- advisory 6b3ad84c-e1a6-4bf7-a703-f496b71e49db
- patch 6b3ad84c-e1a6-4bf7-a703-f496b71e49db
- patch 6b3ad84c-e1a6-4bf7-a703-f496b71e49db
- patch 6b3ad84c-e1a6-4bf7-a703-f496b71e49db
- web 6b3ad84c-e1a6-4bf7-a703-f496b71e49db
- web 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
- web 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
- web 0b0ca135-0b70-47e7-9f44-1890c2a1c46c