CVE-2026-119598

MEDIUMPre-NVD 4.34.3
EchelonGraph scoreHIGH confidence

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

Score 4.3 from GitHub Security Advisory published 2026-10-30. A secondary CVSS source baseline 4.3; sources differ by 0.0.

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

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

4.3EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: —CVSS: 4.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Miaomiaowu before 0.9.3 contains an insecure direct object reference vulnerability in /api/user/proxy-provider-configs that allows authenticated users to read other users' configurations. Attackers can iterate the global auto-increment external_subscription_id parameter to disclose override scripts, filter rules, custom request headers and health-check URLs.

CVSS v3
4.3
EG Score
4.3MEDIUMhigh confidence
EG Risk
19
EG Risk 19/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)
Severity43% × 45%
Impact severity (EG Severity): CVSS 4.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0% × 40%
No KEV listing, EG-KEV tier or EPSS 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 available. Apply it within your standard update timelines.
EPSS PROB
—
EPSS %ILE
—
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 (4.3): severity, escalated by confirmed exploitation. This CVE's 4.3 is its impact severity (EG Severity), not escalated.

EG Severity
4.3 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
Unknown (no EPSS on record)Unknown, not low: FIRST has published no EPSS probability for this CVE.
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: 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 available. 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.

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 30, 2026

Last Modified

October 30, 2026

Advisory Details (8)

Auto-updated Oct 30, 2026
Patch available. Sources: github_release, github_commit.
Web page

Miaomiaowu before 0.9.3 Cross-User Proxy Provider Config Disclosure via external_subscription_id | Advisories | VulnCheck

https://www.vulncheck.com/advisories/miaomiaowu-before-0.9.3-cross-user-proxy-provider-config-disclosure-via-external-subscription-id
Web page

miaomiaowu: cross-user IDOR reads another user's proxy provider configs by subscription id - HackMD

https://hackmd.io/@hieuPenguinnn/miaomiaowu-proxy-provider-config-cross-user-idor
GitHub release Patch Available

v0.9.3

Patch available: iluobei/miaomiaowu v0.9.3

https://github.com/iluobei/miaomiaowu/releases/tag/v0.9.3
Web page

Security vulnerability in iluobei/miaomiaowu: please review the report and fix · Issue #131 · iluobei/miaomiaowu · GitHub

https://github.com/iluobei/miaomiaowu/issues/131
GitHub commit

commit 14ccf37ef82c (iluobei/miaomiaowu)

Fix landed in iluobei/miaomiaowu commit 14ccf37ef82c — awaiting tagged release

https://github.com/iluobei/miaomiaowu/commit/14ccf37ef82cff06b636454c29db7752cdce7cab
Web page

miaomiaowu/internal/storage/traffic.go at v0.9.2 · iluobei/miaomiaowu · GitHub

https://github.com/iluobei/miaomiaowu/blob/v0.9.2/internal/storage/traffic.go#L4808
Web page

miaomiaowu/internal/handler/proxy_provider.go at v0.9.2 · iluobei/miaomiaowu · GitHub

https://github.com/iluobei/miaomiaowu/blob/v0.9.2/internal/handler/proxy_provider.go#L114
Web page

GitHub - iluobei/miaomiaowu: Clash配置订阅管理工具,支持节点管理、生成订阅、导入外部订阅节点、聚合流量、聚合订阅等功能。 · GitHub

https://github.com/iluobei/miaomiaowu

Vendor Advisories for CVE-2026-119598(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 8× in last 7d / 8× 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.

  1. 2026-10-30 16:28 UTCEG score recompute
  2. 2026-10-30 16:28 UTCGHSA enrichmentGHSA-j948-r3jj-xhjm · GitHub CVSS 4.3
  3. 2026-10-30 16:00 UTCEG score recompute
  4. 2026-10-30 16:00 UTCGHSA enrichmentGHSA-j948-r3jj-xhjm · GitHub CVSS 4.3
  5. 2026-10-30 15:02 UTCENISA EUVD ID recordedEUVD-2026-113935 · Source: ENISA EUVD
  6. 2026-10-30 14:27 UTCEG score recompute
  7. 2026-10-30 13:25 UTCEG score recomputeFirst assessed: 4.3 MEDIUM
  8. 2026-10-30 13:25 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-119598?
CVE-2026-119598 is a medium-severity vulnerability; its CVE record was published on October 30, 2026. Miaomiaowu before 0.9.3 contains an insecure direct object reference vulnerability in /api/user/proxy-provider-configs that allows authenticated users to read other users' configurations. Attackers can iterate the global auto-increment externalsubscriptionid parameter to disclose override scripts,…
When was CVE-2026-119598 made public?
CVE-2026-119598 was made public on October 22, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on October 30, 2026. EchelonGraph's copy of the record carries a last-modified date of October 30, 2026; the record at its source may have been updated since.
What is the CVSS score of CVE-2026-119598?
CVE-2026-119598 has a CVSS base score of 4.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-119598?
A fix for CVE-2026-119598 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-119598 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-119598?

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