CVE-2026-54909

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 70% of all CVEs by exploit prediction. 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).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.3Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

pion/stun is a Go implementation of STUN. Prior to 3.1.3, XORMappedAddress.GetFromAs can panic while parsing a malformed short XOR-MAPPED-ADDRESS attribute in STUN or ICE Binding-response parsing paths, allowing remote denial of service. This issue is fixed in version 3.1.3.

CVSS v3
5.3
EG Score
5.3(medium)
EG Risk
39(Track)
EG Risk 39/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 computed
Severity53% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
30%
KEV
Not listed

Published

July 31, 2026

Last Modified

August 3, 2026

Advisory Details (4)

Auto-updated Jul 31, 2026
Patch available. Sources: github, github_pr, github_commit, github_release.
github_release Patch Available

v3.1.3

Patch available: pion/stun v3.1.3

https://github.com/pion/stun/releases/tag/v3.1.3
github_commit Patch Available

commit fa9f074a33a8 (pion/stun)

Patch available: pion/stun v3.1.3 (contains commit fa9f074a33a8)

https://github.com/pion/stun/commit/fa9f074a33a8059c76c960b1fbee39f308002423
github_pr Patch Available

Fix panic on short XOR-MAPPED-ADDRESS value

Patch available: pion/stun v3.1.3 (PR #278 merged 2026-06-02)

https://github.com/pion/stun/pull/278
github Patch Available

Remote denial of service via panic while parsing a malformed XOR-MAPPED-ADDRESS attribute · Advisory · pion/stun · GitHub

https://github.com/pion/stun/security/advisories/GHSA-34rh-wp3j-6cxc

Vendor Advisories for CVE-2026-54909(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(7 across 4 ecosystems)
Go(3)
PackageVulnerable rangeFixed inDependents
github.com/pion/stun———
github.com/pion/stun/v2———
github.com/pion/stun/v3—3.1.5—
Debian:14(2)
PackageVulnerable rangeFixed inDependents
golang-github-pion-stun0.6.1-1, 0.6.1-2——
golang-github-pion-stun-v33.0.0-1, 3.0.2-1, 3.0.2-2——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
golang-github-pion-stun0.4.0-1, 0.6.1-1, 0.6.1-1~bpo12+1, 0.6.1-2——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
golang-github-pion-stun0.6.1-1, 0.6.1-2——

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 13× in last 7d / 40× 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.

  1. 2026-08-21 23:49 UTCEPSS rescore
  2. 2026-08-21 21:55 UTCEG score recompute
  3. 2026-08-20 22:55 UTCEPSS rescore
  4. 2026-08-19 19:04 UTCEG score recompute
  5. 2026-08-19 17:04 UTCEPSS rescore
  6. 2026-08-18 15:50 UTCEG score recompute
  7. 2026-08-18 13:48 UTCEPSS rescore
  8. 2026-08-17 13:47 UTCEPSS rescore
  9. 2026-08-17 12:39 UTCEG score recompute
  10. 2026-08-16 14:56 UTCEPSS rescore
  11. 2026-08-16 11:16 UTCEG score recompute
  12. 2026-08-16 02:14 UTCEPSS rescore
  13. 2026-08-15 09:54 UTCEG score recompute
  14. 2026-08-15 01:30 UTCEPSS rescore
  15. 2026-08-14 08:31 UTCEG score recompute
  16. 2026-08-13 22:00 UTCEPSS rescore
  17. 2026-08-13 07:09 UTCEG score recompute
  18. 2026-08-12 13:51 UTCEPSS rescore
  19. 2026-08-12 05:39 UTCEG score recompute
  20. 2026-08-11 04:17 UTCEG score recompute
  21. 2026-08-11 00:00 UTCEPSS rescore
  22. 2026-08-10 02:54 UTCEG score recompute
  23. 2026-08-09 13:46 UTCEPSS rescore
  24. 2026-08-09 01:32 UTCEG score recompute
  25. 2026-08-08 16:37 UTCEPSS rescore
Show 15 more
  1. 2026-08-08 00:10 UTCEG score recompute
  2. 2026-08-06 22:48 UTCEG score recompute
  3. 2026-08-06 13:47 UTCEPSS rescore
  4. 2026-08-05 21:02 UTCEG score recompute
  5. 2026-08-05 19:17 UTCEPSS rescore
  6. 2026-08-04 19:40 UTCEG score recompute
  7. 2026-08-04 15:10 UTCEPSS rescore
  8. 2026-08-04 10:39 UTCEPSS rescore
  9. 2026-08-03 18:18 UTCEG score recompute
  10. 2026-08-03 18:00 UTCEG score recompute
  11. 2026-08-03 10:36 UTCEPSS rescore
  12. 2026-08-03 02:17 UTCEG score recompute
  13. 2026-08-02 02:27 UTCEPSS rescore
  14. 2026-07-31 23:31 UTCEG score recompute
  15. 2026-07-31 22:07 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-54909?
CVE-2026-54909 is a medium vulnerability published on July 31, 2026. pion/stun is a Go implementation of STUN. Prior to 3.1.3, XORMappedAddress.GetFromAs can panic while parsing a malformed short XOR-MAPPED-ADDRESS attribute in STUN or ICE Binding-response parsing paths, allowing remote denial of service. This issue is fixed in version 3.1.3.
When was CVE-2026-54909 disclosed?
CVE-2026-54909 was first published in the National Vulnerability Database on July 31, 2026, with the most recent update on August 3, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54909 actively exploited?
CVE-2026-54909 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 69.5% of all scored CVEs.
What is the CVSS score of CVE-2026-54909?
CVE-2026-54909 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-54909?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54909, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-54909

Explore →

Is Your Infrastructure Affected by CVE-2026-54909?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs