In MITRE SAF Heimdall 2.11.6 through 2.13.x before 2.14.0, an SSRF issue allows remote attackers to access internal network resources via the Tenable proxy endpoint. This occurs in apps/backend/src/tenable/tenable.controller.ts.
CVE-2026-82477
This medium-severity CVE scores 5.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.8
- EG Score
- 5.8(low)
- EG Risk
- 31(Track)EG Risk 31/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity58% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
August 29, 2026
Last Modified
August 29, 2026
Advisory Details (2)
Auto-updated Aug 29, 2026v2.14.0
Patch available: mitre/heimdall2 v2.14.0
https://github.com/mitre/heimdall2/releases/tag/v2.14.0commit b6a9cdb4fc01 (mitre/heimdall2)
Fix landed in mitre/heimdall2 commit b6a9cdb4fc01 — awaiting tagged release
https://github.com/mitre/heimdall2/commit/b6a9cdb4fc01f96aaa1a77cc27d1d449b485937bVendor Advisories for CVE-2026-82477(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 3× in last 7d / 3× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-29 15:24 UTCEG score recompute
- 2026-08-29 14:25 UTCEG score recompute
- 2026-08-29 14:22 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-918
- CVE-2016-10927EG 10.0CRITICAL
- CVE-2016-10926EG 10.0CRITICAL
- CVE-2018-10511EG 10.0CRITICAL
- CVE-2018-1000124EG 10.0CRITICAL
- CVE-2017-11291EG 10.0EPSS p91CRITICAL
- CVE-2017-12905EG 10.0CRITICAL
- CVE-2017-8794EG 10.0CRITICAL
- CVE-2017-13667EG 9.9CRITICAL
- CVE-2017-17674EG 9.8CRITICAL
- CVE-2013-4864EG 9.8EPSS p93CRITICAL
Frequently asked(4)
What is CVE-2026-82477?
When was CVE-2026-82477 disclosed?
What is the CVSS score of CVE-2026-82477?
How do I remediate CVE-2026-82477?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-82477
Is Your Infrastructure Affected by CVE-2026-82477?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.