CVE-2026-91129

MEDIUMPre-NVD 5.45.4
EchelonGraph scoreMEDIUM confidence

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

Score 5.4 from GitHub Security Advisory (severity: MODERATE) published 2026-09-22. A secondary CVSS source baseline 5.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this weekElevated

Also known asEUVD-2026-84804 (ENISA EUVD) · GHSA-4ghv-53cq-7wp3 (GitHub Security Advisories) · PYSEC-2026-4051 (OSV.dev)Source: ENISA EUVD

5.4EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 5.4Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Home Assistant is open source home automation software focused on local control and privacy. Prior to 2026.2.3, the IPP integration automatically processed unauthenticated _ipp._tcp.local mDNS announcements in homeassistant/components/ipp/config_flow.py, where async_step_zeroconf passed attacker-controlled host, port, and base_path values to validate_input for printer metadata retrieval. Because the shared HTTP client followed attacker-controlled cross-origin redirects without blocking loopback targets, a local-network attacker could redirect the request to 127.0.0.1 or another internal service without user interaction or prior IPP configuration. This issue is fixed in version 2026.2.3.

CVSS v3
5.4
EG Score
5.4MEDIUMmedium confidence
EG Risk
40
EG Risk 40/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)
Severity54% × 45%
Impact severity (EG Severity): CVSS 5.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (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: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
22nd
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 (5.4): severity, escalated by confirmed exploitation. This CVE's 5.4 is its impact severity (EG Severity), not escalated.

EG Severity
5.4 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). 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 low or medium mission impact; Track* at high (mission-essential systems).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 low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (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

September 22, 2026

Last Modified

September 25, 2026

Advisory Details (5)

Auto-updated Sep 22, 2026
Patch available. Sources: github, github_pr, github_commit, github_release.
GitHub release Patch Available

2026.2.3

Patch available: home-assistant/core 2026.2.3

https://github.com/home-assistant/core/releases/tag/2026.2.3
GitHub commit Patch Available

commit 815c708d19aa (home-assistant/core)

Patch available: home-assistant/core 2026.7.0 (contains commit 815c708d19aa)

https://github.com/home-assistant/core/commit/815c708d19aa0c7f59f9ee318b613a5e481a42b3
GitHub commit Patch Available

commit 0f3c7ca2772b (home-assistant/core)

Patch available: home-assistant/core 2026.7.0 (contains commit 0f3c7ca2772b)

https://github.com/home-assistant/core/commit/0f3c7ca2772b605c0f3c09c88f35e527ea6ea560
GitHub pull request Patch Available

Block redirect to localhost

Patch available: home-assistant/core 2026.7.0 (PR #162941 merged 2026-02-13)

https://github.com/home-assistant/core/pull/162941
GitHub advisoryMentions a patch (unverified)

mDNS Server-Side Request Forgery · Advisory · home-assistant/core · GitHub

https://github.com/home-assistant/core/security/advisories/GHSA-4ghv-53cq-7wp3

Vendor Advisories for CVE-2026-91129(1)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
piphomeassistant @ 2026.2.3 (fixes < 2026.2.2)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
homeassistant0.10.0 ... 2026.2.2 (1542 versions)
  • every version up to 2026.2.3: fixed in 2026.2.3
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 47× 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 it from the CNA feed. 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). Most recent first.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 69 is merged into the row it repeats.

  1. 2026-11-01 16:36 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  2. 2026-11-01 07:37 UTCGHSA enrichmentGHSA-4ghv-53cq-7wp3 · GitHub severity MODERATE · GitHub CVSS 5.4
  3. 2026-11-01 07:37 UTCEG score recompute
  4. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  5. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  6. 2026-10-29 22:25 UTCOSV refresh
  7. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  8. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  9. 2026-10-27 16:33 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  10. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  11. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  12. 2026-10-25 13:51 UTCEG score recompute
  13. 2026-10-24 16:34 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  14. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  15. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  16. 2026-10-22 12:30 UTCEG score recompute
  17. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  18. 2026-10-20 16:34 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  19. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  20. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  21. 2026-10-18 03:00 UTCEG score recompute
  22. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  23. 2026-10-16 16:45 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  24. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  25. 2026-10-14 16:34 UTCEPSS rescoreEPSS 0.2% · 9th percentile
Show 43 more
  1. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  2. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  3. 2026-10-12 14:46 UTCEG score recompute
  4. 2026-10-11 19:13 UTCEG score recompute
  5. 2026-10-11 16:30 UTCEG score recompute
  6. 2026-10-11 13:50 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  7. 2026-10-11 13:44 UTCEG score recompute
  8. 2026-10-11 01:40 UTCEG score recompute
  9. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  10. 2026-10-10 02:06 UTCEG score recompute
  11. 2026-10-09 20:08 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  12. 2026-10-09 02:58 UTCEG score recompute
  13. 2026-10-08 17:14 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  14. 2026-10-08 03:50 UTCEG score recompute
  15. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  16. 2026-10-07 04:42 UTCEG score recompute
  17. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  18. 2026-10-06 05:33 UTCEG score recompute
  19. 2026-10-05 17:44 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  20. 2026-10-05 06:20 UTCEG score recompute
  21. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  22. 2026-10-04 07:11 UTCEG score recompute
  23. 2026-10-03 08:03 UTCEG score recompute
  24. 2026-10-02 08:55 UTCEG score recompute
  25. 2026-10-01 19:51 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  26. 2026-10-01 09:46 UTCEG score recompute
  27. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  28. 2026-09-30 10:38 UTCEG score recompute
  29. 2026-09-29 11:26 UTCEG score recompute
  30. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  31. 2026-09-28 12:18 UTCEG score recompute
  32. 2026-09-27 13:49 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  33. 2026-09-27 13:10 UTCEG score recompute
  34. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  35. 2026-09-26 14:02 UTCEG score recompute
  36. 2026-09-24 16:38 UTCEG score recompute
  37. 2026-09-24 15:32 UTCEG score recompute
  38. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  39. 2026-09-23 19:06 UTCEG score recompute
  40. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  41. 2026-09-22 19:37 UTCEG score recompute
  42. 2026-09-22 19:08 UTCEG score recomputeFirst assessed: 5.4 MEDIUM
  43. 2026-09-22 19:08 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-91129?
CVE-2026-91129 is a medium-severity vulnerability; its CVE record was published on September 22, 2026. Home Assistant is open source home automation software focused on local control and privacy. Prior to 2026.2.3, the IPP integration automatically processed unauthenticated _ipp._tcp.local mDNS announcements in homeassistant/components/ipp/config_flow.py, where async_step_zeroconf passed…
When was the CVE record for CVE-2026-91129 published?
The CVE record for CVE-2026-91129 was published on September 22, 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 September 25, 2026; the record at its source may have been updated since.
Is CVE-2026-91129 actively exploited?
CVE-2026-91129 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (22nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-91129?
CVE-2026-91129 has a CVSS base score of 5.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-91129?
A fix for CVE-2026-91129 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-91129 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-91129

Explore →

Is Your Infrastructure Affected by CVE-2026-91129?

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