CVE-2026-118173

MEDIUMPre-NVD 6.16.1
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 6.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (22nd 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-111350 (ENISA EUVD) · GHSA-v5vh-f252-qp24 (GitHub Security Advisories)Source: ENISA EUVD

6.1EG
EchelonGraph verdictMonitorNo release containing the referenced fix is confirmed: check the referenced fix and the vendor's advisory for a release that contains it; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 6.1Exploit: None knownExposed services: Not assessed

A fix is referenced (a reference tagged "Patch", often a source commit), but no release containing it is confirmed — find the release that contains it; until it is applied, mitigate (WAF / firewall / segmentation).

MISP Guard, a proxy that enforces security policies on MISP feed data, contained an incomplete validation check for required taxonomy tags. When a feed event or its attributes carried tags belonging to a required taxonomy (for example, TLP), the guard only verified that at least one tag of that taxonomy matched the configured allowed list. It did not verify that every tag of the required taxonomy present on the event or attribute was in the allowed list. As a result, an event or attribute could simultaneously carry an allowed tag (e.g., tlp:clear) and a non-allowed tag (e.g., tlp:red or tlp:amber) and still pass the guard's policy check. This allowed data marked with a higher classification or sensitivity level to be distributed through feeds configured to only distribute lower-classification data, effectively bypassing the intended data-handling restrictions. The vulnerability affected both event-level and attribute-level tag validation, including attributes nested within objects and shadow attributes. An attacker with the ability to author or modify MISP events in a feed source could include non-allowed taxonomy tags alongside allowed ones to exfiltrate more sensitive data to feed consumers than the guard policy intended to permit.

CVSS
6.1
EG Score
6.1MEDIUMmedium confidence
EG Risk
28
EG Risk 28/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)
Severity61% × 45%
Impact severity (EG Severity): CVSS 6.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 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: A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule.
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 (6.1): severity, escalated by confirmed exploitation. This CVE's 6.1 is its impact severity (EG Severity), not escalated.

EG Severity
6.1 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-10). 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.No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.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.

A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule.

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.

No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.

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

October 27, 2026

Last Modified

November 4, 2026

References (1)

Vendor Advisories for CVE-2026-118173(1)

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

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 24× 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 → 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.3% · 22nd percentile
  2. 2026-11-12 16:33 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  3. 2026-11-11 16:38 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  4. 2026-11-11 06:55 UTCEchelonGraph re-scored
  5. 2026-11-11 06:54 UTCGHSA enrichmentGHSA-v5vh-f252-qp24 · GitHub severity MODERATE
  6. 2026-11-10 16:42 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  7. 2026-11-09 16:34 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  8. 2026-11-08 16:38 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  9. 2026-11-07 16:38 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  10. 2026-11-06 16:36 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  11. 2026-11-05 16:36 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  12. 2026-11-04 17:27 UTCEchelonGraph re-scored
  13. 2026-11-04 17:27 UTCGHSA enrichmentGHSA-v5vh-f252-qp24 · GitHub severity MODERATE
  14. 2026-11-04 16:46 UTCEchelonGraph re-scored
  15. 2026-11-04 16:46 UTCGHSA enrichmentGHSA-v5vh-f252-qp24 · GitHub severity MODERATE
  16. 2026-11-04 16:34 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  17. 2026-11-04 01:48 UTCEchelonGraph re-scored
  18. 2026-11-04 01:48 UTCGHSA enrichmentGHSA-v5vh-f252-qp24 · GitHub severity MODERATE
  19. 2026-11-03 16:46 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  20. 2026-11-02 16:44 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  21. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  22. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  23. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  24. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  25. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
Show 5 more
  1. 2026-10-28 15:26 UTCGHSA enrichmentGHSA-v5vh-f252-qp24
  2. 2026-10-27 19:26 UTCEchelonGraph re-scored
  3. 2026-10-27 19:01 UTCENISA EUVD ID recordedEUVD-2026-111350 · Source: ENISA EUVD
  4. 2026-10-27 18:20 UTCEchelonGraph re-scoredFirst assessed: 6.1 MEDIUM
  5. 2026-10-27 18:19 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-118173?
CVE-2026-118173 is a medium-severity vulnerability; its CVE record was published on October 27, 2026. MISP Guard, a proxy that enforces security policies on MISP feed data, contained an incomplete validation check for required taxonomy tags. When a feed event or its attributes carried tags belonging to a required taxonomy (for example, TLP), the guard only verified that at least one tag of that…
When was the CVE record for CVE-2026-118173 published?
The CVE record for CVE-2026-118173 was published on October 27, 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 4, 2026; the record at its source may have been updated since.
Is CVE-2026-118173 actively exploited?
CVE-2026-118173 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-118173?
CVE-2026-118173 has a CVSS base score of 6.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-118173?
A fix for CVE-2026-118173 is referenced (a reference tagged "Patch", often a source commit), but EchelonGraph has no release containing it on record. Check that reference and the vendor's advisory for a release that contains the fix and update to it; until then, restrict network exposure of the affected system or apply the vendor's mitigation. The vendor advisories EchelonGraph has for CVE-2026-118173 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-118173?

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

Book a Demo →Browse All CVEs