CVE-2026-113783

HIGHPre-NVD 7.47.4
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 7.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (29th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source

Also known asEUVD-2026-117052 (ENISA EUVD)Source: ENISA EUVD

7.4EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.4Exploit: None knownExposed services: Not assessed

The CVE record names the fixed release — apply it.

ESP-IDF is the Espressif Internet of Things (IOT) Development Framework. From 5.2.3 until 5.3.7, 5.4.5, 5.5.6, and 6.0.3, the lwIP DNS resolver's cached-lookup path in dns_lookup() in dns.c copies every cached address into a caller-provided single ip_addr_t output buffer without a length parameter or bounds check. When CONFIG_LWIP_DNS_MAX_HOST_IP is greater than 1 and a cached hostname has multiple A or AAAA records, a subsequent lookup through dns_gethostbyname() or dns_gethostbyname_addrtype() writes beyond the single-element buffer into adjacent stack memory. A network-positioned attacker who influences DNS responses can cause a reboot through stack-canary corruption or, without stack protection, overwrite stack variables with attacker-controlled address bytes and potentially redirect control flow. This issue is fixed in versions 5.5.6 and 6.0.3 and is scheduled to be fixed in versions 5.3.7 and 5.4.5. No fixed release is available for the end-of-life 5.2 line.

CVSS v3
7.4
EG Score
7.4HIGHmedium confidence
EG Risk
33
EG Risk 33/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity74% × 45%
Impact severity (EG Severity): CVSS 7.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: The CVE record names the fixed release. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
29th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.4): severity, escalated by confirmed exploitation. This CVE's 7.4 is its impact severity (EG Severity), not escalated.

EG Severity
7.4 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

The CVE record names the fixed release. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

November 4, 2026

Last Modified

November 12, 2026

Advisory Details (7)

Auto-updated Nov 7, 2026
Fix named in the CVE record. Sources: github, github_commit.
GitHub advisoryMentions a patch (unverified)

Stack-Based Buffer Overflow in lwIP DNS Cache Lookup with Multiple IP Addresses · Advisory · espressif/esp-idf · GitHub

https://github.com/espressif/esp-idf/security/advisories/GHSA-ch63-jxm5-vmvf
GitHub commit

commit defaa2f55947 (espressif/esp-idf)

Fix landed in espressif/esp-idf commit defaa2f55947 — awaiting tagged release

https://github.com/espressif/esp-idf/commit/defaa2f559470acfee5e2e5ea80a79b73424d483
GitHub commit

commit af7543d00a4d (espressif/esp-idf)

Fix landed in espressif/esp-idf commit af7543d00a4d — awaiting tagged release

https://github.com/espressif/esp-idf/commit/af7543d00a4d7b489e010a70b59fd3d8022a40f4
GitHub commit

commit 98e6e7a08fca (espressif/esp-idf)

Fix landed in espressif/esp-idf commit 98e6e7a08fca — awaiting tagged release

https://github.com/espressif/esp-idf/commit/98e6e7a08fca391563651a1e751cc45a3b27d18b
GitHub commit

commit 882843dbf838 (espressif/esp-idf)

Fix landed in espressif/esp-idf commit 882843dbf838 — awaiting tagged release

https://github.com/espressif/esp-idf/commit/882843dbf838b0c02e09d46bb6283bda73496b8c
GitHub commit

commit 7ab85eb4dc7d (espressif/esp-idf)

Fix landed in espressif/esp-idf commit 7ab85eb4dc7d — awaiting tagged release

https://github.com/espressif/esp-idf/commit/7ab85eb4dc7d7695960d940badcd62592c365056
GitHub commit

commit 75f2ff7e0c2d (espressif/esp-idf)

Fix landed in espressif/esp-idf commit 75f2ff7e0c2d — awaiting tagged release

https://github.com/espressif/esp-idf/commit/75f2ff7e0c2d19e113293ec122b701c83d2f6665

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 11× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-13 16:50 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  2. 2026-11-12 20:28 UTCEchelonGraph re-scored
  3. 2026-11-12 16:33 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  4. 2026-11-11 16:38 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  5. 2026-11-10 16:42 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  6. 2026-11-09 17:27 UTCEchelonGraph re-scored
  7. 2026-11-09 17:00 UTCEchelonGraph re-scored
  8. 2026-11-09 16:34 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  9. 2026-11-08 16:38 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  10. 2026-11-07 16:38 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  11. 2026-11-06 16:36 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  12. 2026-11-05 16:36 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  13. 2026-11-04 20:03 UTCENISA EUVD ID recordedEUVD-2026-117052 · Source: ENISA EUVD
  14. 2026-11-04 19:26 UTCEchelonGraph re-scored
  15. 2026-11-04 19:15 UTCEchelonGraph re-scoredFirst assessed: 7.4 HIGH
  16. 2026-11-04 19:15 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-113783?
CVE-2026-113783 is a high-severity vulnerability; its CVE record was published on November 4, 2026. ESP-IDF is the Espressif Internet of Things (IOT) Development Framework. From 5.2.3 until 5.3.7, 5.4.5, 5.5.6, and 6.0.3, the lwIP DNS resolver's cached-lookup path in dns_lookup() in dns.c copies every cached address into a caller-provided single ip_addr_t output buffer without a length parameter…
When was the CVE record for CVE-2026-113783 published?
The CVE record for CVE-2026-113783 was published on November 4, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 12, 2026; the record at its source may have been updated since.
Is CVE-2026-113783 actively exploited?
CVE-2026-113783 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (29th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-113783?
CVE-2026-113783 has a CVSS base score of 7.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-113783?
The CVE record for CVE-2026-113783 names the fix: "This issue is fixed in versions 5.5.6 and 6.0.3 and is scheduled to be fixed in versions 5.3.7 and 5.4.5."

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-113783?

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

Book a Demo →Browse All CVEs