CVE-2026-3416

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 82% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

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

The API Publisher component previously used a non-cryptographic pseudorandom number generator (PRNG) to create shared secrets for Webhook HMAC validation. This PRNG lacks sufficient entropy for security-sensitive operations, allowing a sophisticated attacker to predict future secrets. This enables malicious actors to forge event payloads with valid HMAC signatures, bypassing the API Gateway's authenticity verification.

Successful exploitation could allow an attacker to predict shared secrets used for Webhook HMAC validation and forge event payloads with valid signatures. This may enable bypassing API Gateway authenticity checks, leading to unauthorized event injection, data manipulation, or downstream system compromise.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
34(Track)
EG Risk 34/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
Severity75% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
18%
KEV
Not listed

Published

September 3, 2026

Last Modified

September 15, 2026

References (1)

Vendor Advisories for CVE-2026-3416(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 26× in last 7d / 52× 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-09-19 09:56 UTCGHSA enrichment
  2. 2026-09-18 21:24 UTCEG score recompute
  3. 2026-09-18 21:24 UTCGHSA enrichment
  4. 2026-09-18 19:28 UTCEPSS rescore
  5. 2026-09-18 19:28 UTCEPSS rescore
  6. 2026-09-18 08:30 UTCGHSA enrichment
  7. 2026-09-17 20:36 UTCEG score recompute
  8. 2026-09-17 20:36 UTCGHSA enrichment
  9. 2026-09-17 19:30 UTCEPSS rescore
  10. 2026-09-17 06:46 UTCGHSA enrichment
  11. 2026-09-16 18:35 UTCEG score recompute
  12. 2026-09-16 18:35 UTCGHSA enrichment
  13. 2026-09-16 14:08 UTCEPSS rescore
  14. 2026-09-16 06:07 UTCEG score recompute
  15. 2026-09-16 06:07 UTCGHSA enrichment
  16. 2026-09-16 05:15 UTCEPSS rescore
  17. 2026-09-15 18:14 UTCEG score recompute▲ 1.60
  18. 2026-09-15 18:13 UTCGHSA enrichment
  19. 2026-09-15 18:11 UTCNVD updateCVSS v3 → 7.5 · severity → HIGH
  20. 2026-09-15 03:11 UTCEPSS rescore
  21. 2026-09-14 19:43 UTCGHSA enrichment
  22. 2026-09-13 20:28 UTCEG score recompute
  23. 2026-09-13 20:28 UTCGHSA enrichment
  24. 2026-09-13 16:47 UTCEPSS rescore
  25. 2026-09-12 21:13 UTCEG score recompute
Show 27 more
  1. 2026-09-12 21:13 UTCGHSA enrichment
  2. 2026-09-12 15:01 UTCEPSS rescore
  3. 2026-09-11 21:58 UTCEG score recompute
  4. 2026-09-11 21:58 UTCGHSA enrichment
  5. 2026-09-11 14:53 UTCEPSS rescore
  6. 2026-09-11 09:37 UTCEPSS rescore
  7. 2026-09-10 22:43 UTCEG score recompute
  8. 2026-09-10 22:43 UTCGHSA enrichment
  9. 2026-09-10 09:34 UTCEPSS rescore
  10. 2026-09-09 23:28 UTCGHSA enrichment
  11. 2026-09-08 23:09 UTCEG score recompute
  12. 2026-09-08 23:09 UTCGHSA enrichment
  13. 2026-09-08 22:00 UTCEPSS rescore
  14. 2026-09-07 15:01 UTCGHSA enrichment
  15. 2026-09-06 15:47 UTCEG score recompute
  16. 2026-09-06 15:47 UTCGHSA enrichment
  17. 2026-09-06 13:47 UTCEPSS rescore
  18. 2026-09-05 16:31 UTCEG score recompute
  19. 2026-09-05 16:31 UTCGHSA enrichment
  20. 2026-09-04 17:14 UTCEG score recompute
  21. 2026-09-04 17:14 UTCGHSA enrichment
  22. 2026-09-03 17:59 UTCEG score recompute
  23. 2026-09-03 17:59 UTCGHSA enrichment
  24. 2026-09-03 13:14 UTCEG score recompute
  25. 2026-09-03 13:02 UTCEG score recompute
  26. 2026-09-03 12:47 UTCEG score recompute
  27. 2026-09-03 12:44 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-3416?
CVE-2026-3416 is a high vulnerability published on September 3, 2026. The API Publisher component previously used a non-cryptographic pseudorandom number generator (PRNG) to create shared secrets for Webhook HMAC validation. This PRNG lacks sufficient entropy for security-sensitive operations, allowing a sophisticated attacker to predict future secrets. This enables…
When was CVE-2026-3416 disclosed?
CVE-2026-3416 was first published in the National Vulnerability Database on September 3, 2026, with the most recent update on September 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-3416 actively exploited?
CVE-2026-3416 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 81.9% of all scored CVEs.
What is the CVSS score of CVE-2026-3416?
CVE-2026-3416 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-3416?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-3416, 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

Explore the affected products and dependency analysis for CVE-2026-3416

Explore →

Is Your Infrastructure Affected by CVE-2026-3416?

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

Start Free Scan →Browse All CVEs