CVE-2026-49457

CRITICALPre-NVD 9.19.1—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 96% 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
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 9.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

erlang_quic is a pure Erlang QUIC implementation. Prior to version 1.4.4, the QUIC client did not authenticate the server during the TLS 1.3 handshake. The CertificateVerify signature was not checked, the certificate chain was not validated, and the hostname was not compared against the certificate, so verify was effectively a no-op on the client. A man-in-the-middle on the network path could present any certificate and impersonate any server, defeating the confidentiality and integrity of the connection. HTTP/3 uses the same client and was equally affected. Handshakes authenticated by a PSK (session resumption) are not affected, because the peer is authenticated by the PSK binder and no certificate is sent. This is fixed in 1.4.4. The client now verifies the CertificateVerify signature, validates the certificate chain against the trust store (cacerts option, the operating system store by default), and checks the hostname. Client verify now defaults to on; set verify => false to accept any certificate (for example a self-signed test server). No known workarounds are available before 1.4.4. verify => true had no effect, and inspecting the certificate after connecting does not help because without the signature check the peer is never proven to own the certificate it presents.

CVSS v3
9.1
EG Score
9.1CRITICALmedium confidence
EG Risk
56
EG Risk 56/100

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
Severity91% × 45%
Exploitation0% × 40%
Automatability100% × 15%
EPSS PROB
0.2%
EPSS %ILE
14th
KEV
Not listed

Published

July 1, 2026

Last Modified

September 18, 2026

Advisory Details (1)

Auto-updated Sep 16, 2026
Patch available. Sources: github.
githubMentions a patch (unverified)

Broken TLS verification · Advisory · benoitc/erlang_quic · GitHub

Affected: 1.4.4. The client now verifies the CertificateVerify signature, validates the cer

https://github.com/benoitc/erlang_quic/security/advisories/GHSA-2r8v-p65x-3663

Vendor Advisories for CVE-2026-49457(1)

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

Affected Packages

(1 across 1 ecosystem)
Hex(1)
PackageVulnerable rangeFix by version rangeDependents
quic0.10.0 ... 1.4.3 (25 versions)
  • every version up to 1.4.4: fixed in 1.4.4
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 27× 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-10-09 20:07 UTCEPSS rescore
  2. 2026-10-08 17:12 UTCEPSS rescore
  3. 2026-10-07 23:48 UTCEPSS rescore
  4. 2026-10-06 15:18 UTCEPSS rescore
  5. 2026-10-05 17:43 UTCEPSS rescore
  6. 2026-10-04 23:22 UTCEPSS rescore
  7. 2026-10-03 14:25 UTCEPSS rescore
  8. 2026-10-01 19:50 UTCEPSS rescore
  9. 2026-09-30 15:03 UTCEPSS rescore
  10. 2026-09-28 13:51 UTCEPSS rescore
  11. 2026-09-27 13:48 UTCEPSS rescore
  12. 2026-09-26 15:59 UTCEPSS rescore
  13. 2026-09-26 00:27 UTCEPSS rescore
  14. 2026-09-23 17:53 UTCEPSS rescore
  15. 2026-09-23 06:48 UTCEG score recompute
  16. 2026-09-20 20:16 UTCEPSS rescore
  17. 2026-09-18 20:36 UTCEG score recompute
  18. 2026-09-18 19:28 UTCEPSS rescore
  19. 2026-09-18 06:28 UTCEG score recompute
  20. 2026-09-16 14:08 UTCEPSS rescore
  21. 2026-09-16 05:15 UTCEPSS rescore
  22. 2026-09-14 00:21 UTCEG score recompute
  23. 2026-09-13 16:47 UTCEPSS rescore
  24. 2026-09-13 09:07 UTCEG score recompute
  25. 2026-09-12 14:36 UTCEG score recompute
Show 45 more
  1. 2026-09-11 14:53 UTCEPSS rescore
  2. 2026-09-10 09:35 UTCEPSS rescore
  3. 2026-09-08 22:01 UTCEPSS rescore
  4. 2026-09-07 16:01 UTCEPSS rescore
  5. 2026-09-06 14:26 UTCEG score recompute
  6. 2026-09-06 13:47 UTCEPSS rescore
  7. 2026-09-06 00:45 UTCEG score recompute
  8. 2026-09-04 05:06 UTCEPSS rescore
  9. 2026-09-02 14:12 UTCEPSS rescore
  10. 2026-09-01 13:54 UTCEPSS rescore
  11. 2026-09-01 04:40 UTCEPSS rescore
  12. 2026-08-30 21:07 UTCEG score recompute
  13. 2026-08-30 19:17 UTCEPSS rescore
  14. 2026-08-30 11:43 UTCEG score recompute
  15. 2026-08-30 01:22 UTCEPSS rescore
  16. 2026-08-28 21:41 UTCEPSS rescore
  17. 2026-08-27 22:24 UTCEG score recompute
  18. 2026-08-27 14:25 UTCEPSS rescore
  19. 2026-08-26 14:46 UTCEPSS rescore
  20. 2026-08-25 16:16 UTCEG score recompute
  21. 2026-08-25 13:49 UTCEPSS rescore
  22. 2026-08-24 14:54 UTCEG score recompute
  23. 2026-08-24 10:49 UTCEG score recompute
  24. 2026-08-23 03:59 UTCEG score recompute
  25. 2026-08-23 00:19 UTCEPSS rescore
  26. 2026-08-22 01:22 UTCEG score recompute
  27. 2026-08-21 23:49 UTCEPSS rescore
  28. 2026-08-21 01:01 UTCEG score recompute
  29. 2026-08-20 22:55 UTCEPSS rescore
  30. 2026-08-20 04:36 UTCEG score recompute
  31. 2026-08-19 17:04 UTCEPSS rescore
  32. 2026-08-18 20:57 UTCEG score recompute
  33. 2026-08-18 13:48 UTCEPSS rescore
  34. 2026-08-17 17:08 UTCEG score recompute
  35. 2026-08-17 13:47 UTCEPSS rescore
  36. 2026-08-16 16:50 UTCEG score recompute
  37. 2026-08-16 14:56 UTCEPSS rescore
  38. 2026-08-16 04:42 UTCEG score recompute
  39. 2026-08-16 02:14 UTCEPSS rescore
  40. 2026-08-14 20:19 UTCEG score recompute
  41. 2026-08-14 19:36 UTCEG score recompute
  42. 2026-07-30 10:09 UTCEG score recompute
  43. 2026-07-26 13:13 UTCEG score recompute
  44. 2026-07-23 03:18 UTCEG score recompute
  45. 2026-07-01 21:02 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-49457?
CVE-2026-49457 is a critical vulnerability published on July 1, 2026. erlang_quic is a pure Erlang QUIC implementation. Prior to version 1.4.4, the QUIC client did not authenticate the server during the TLS 1.3 handshake. The CertificateVerify signature was not checked, the certificate chain was not validated, and the hostname was not compared against the…
When was CVE-2026-49457 disclosed?
CVE-2026-49457 was first published on July 1, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-49457 actively exploited?
CVE-2026-49457 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (14th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-49457?
CVE-2026-49457 has a CVSS base score of 9.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-49457?
A fix for CVE-2026-49457 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-49457 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-49457?

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

Book a Demo →Browse All CVEs