CVE-2026-57053

LOWNVD 2.54.0▲
EchelonGraph scoreMEDIUM confidence

Score 4.0 from GitHub Security Advisory published 2026-06-23. NVD baseline CVSS 2.5; sources differ by 1.5.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 3 sources updated this week
2.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 2.5Exploit: NoneExposed: 0

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

GNU libidn before 1.44 is prone to out-of-bounds reads of uninitialized memory in the ToUnicode APIs because of mishandling in idna_to_unicode_internal. The affected code is not present in libidn2.

CVSS v3
2.5
EG Score
4.0(medium)
EPSS
1.5%
KEV
Not listed

Published

June 23, 2026

Last Modified

June 29, 2026

Advisory Details (2)

Auto-updated Jun 25, 2026
🔬 Proof of concept available. No patch confirmed yet.
generic🟡 PoC Available

GNU Libidn Security Advisory: Read out of bounds in ToUnicode APIs

https://lists.gnu.org/archive/html/help-libidn/2026-06/msg00001.html
generic

Security issue: Libidn ToUnicode round-trip verification reads uninitial

https://lists.gnu.org/archive/html/help-libidn/2026-05/msg00000.html

Vendor Advisories for CVE-2026-57053(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 22× in last 7d / 41× 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-07-06 14:06 UTCEG score recompute
  2. 2026-07-06 14:06 UTCGHSA enrichment
  3. 2026-07-06 02:23 UTCEPSS rescore
  4. 2026-07-06 02:23 UTCEPSS rescore
  5. 2026-07-05 14:32 UTCEG score recompute
  6. 2026-07-05 14:31 UTCGHSA enrichment
  7. 2026-07-05 02:31 UTCEPSS rescore
  8. 2026-07-05 02:30 UTCEPSS rescore
  9. 2026-07-04 14:58 UTCEG score recompute
  10. 2026-07-04 14:58 UTCGHSA enrichment
  11. 2026-07-04 06:31 UTCEPSS rescore
  12. 2026-07-04 06:31 UTCEPSS rescore
  13. 2026-07-03 15:25 UTCEG score recompute
  14. 2026-07-03 15:24 UTCGHSA enrichment
  15. 2026-07-02 15:51 UTCEG score recompute
  16. 2026-07-02 15:51 UTCGHSA enrichment
  17. 2026-07-01 16:17 UTCEG score recompute
  18. 2026-07-01 16:17 UTCGHSA enrichment
  19. 2026-07-01 15:07 UTCEPSS rescore
  20. 2026-06-30 23:22 UTCEPSS rescore
  21. 2026-06-30 16:44 UTCEG score recompute
  22. 2026-06-30 16:44 UTCGHSA enrichment
  23. 2026-06-29 20:05 UTCNVD updateCVSS v3 → 2.5 · severity → LOW
  24. 2026-06-29 17:11 UTCEG score recompute
  25. 2026-06-29 17:11 UTCGHSA enrichment
Show 16 more
  1. 2026-06-28 17:32 UTCEG score recompute
  2. 2026-06-28 17:32 UTCGHSA enrichment
  3. 2026-06-28 14:07 UTCEPSS rescore
  4. 2026-06-27 17:58 UTCEG score recompute
  5. 2026-06-27 17:58 UTCGHSA enrichment
  6. 2026-06-27 03:08 UTCEPSS rescore
  7. 2026-06-26 18:25 UTCEG score recompute
  8. 2026-06-26 18:25 UTCGHSA enrichment
  9. 2026-06-25 18:52 UTCEG score recompute
  10. 2026-06-25 18:52 UTCGHSA enrichment
  11. 2026-06-25 13:49 UTCEPSS rescore
  12. 2026-06-24 19:19 UTCEG score recompute
  13. 2026-06-24 19:18 UTCGHSA enrichment
  14. 2026-06-24 14:05 UTCEPSS rescore
  15. 2026-06-23 19:20 UTCEG score recompute
  16. 2026-06-23 19:20 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-57053?
CVE-2026-57053 is a low vulnerability published on June 23, 2026. GNU libidn before 1.44 is prone to out-of-bounds reads of uninitialized memory in the ToUnicode APIs because of mishandling in idnatounicode_internal. The affected code is not present in libidn2.
When was CVE-2026-57053 disclosed?
CVE-2026-57053 was first published in the National Vulnerability Database on June 23, 2026, with the most recent update on June 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-57053 actively exploited?
CVE-2026-57053 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-57053?
CVE-2026-57053 has a CVSS v3 base score of 2.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 4.0.
How do I remediate CVE-2026-57053?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-57053, 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-57053

Explore →

Is Your Infrastructure Affected by CVE-2026-57053?

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

Start Free Scan →Browse All CVEs