CVE-2026-57496

CRITICALPre-NVD 9.69.6
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (37th 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
Elevated

Also known asEUVD-2026-102319 (ENISA EUVD) · GHSA-hxpf-9xvq-wph8 (GitHub Security Advisories)Source: ENISA EUVD

9.6EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (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.4%CVSS: 9.6Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

NetLicensing MCP Server is a natural-language interface that enables agentic applications to manage the software-licensing lifecycle in Labs64 NetLicensing. Prior to 0.1.8, netlicensing_get_product passes the caller-controlled product_number to src/netlicensing_mcp/tools/products.py, which interpolates it into a REST path consumed by nl_get() in src/netlicensing_mcp/client.py without path-segment validation. A traversal segment can be normalized from the intended product path to the /token endpoint, after which the response is serialized through _wrap_json instead of _wrap_json_token_read, bypassing redact_token_read() protections for APIKEY number and SHOP shopURL fields. An authenticated MCP client with a non-administrative API key can retrieve plaintext token values, and a recovered administrative token can provide broad read, write, and delete access to the NetLicensing account. This issue is fixed in version 0.1.8.

CVSS v3
9.6
EG Score
9.6CRITICALmedium confidence
EG Risk
59
EG Risk 59/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)
Severity96% × 45%
Impact severity (EG Severity): CVSS 9.6 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, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
37th
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 (9.6): severity, escalated by confirmed exploitation. This CVE's 9.6 is its impact severity (EG Severity), not escalated.

EG Severity
9.6 CRITICALCVSS-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-10-26). 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, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 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 low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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)14 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 total (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

June 18, 2026

Last Modified

October 21, 2026

Advisory Details (4)

Auto-updated Oct 15, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_pr, github_commit, github_release.
GitHub release Patch Available

0.1.8

Patch available: Labs64/NetLicensing-MCP 0.1.8

https://github.com/Labs64/NetLicensing-MCP/releases/tag/0.1.8
GitHub commit Patch Available

commit b8fd0ea76d53 (Labs64/NetLicensing-MCP)

Patch available: Labs64/NetLicensing-MCP 0.1.8 (contains commit b8fd0ea76d53)

https://github.com/Labs64/NetLicensing-MCP/commit/b8fd0ea76d533202573eb24add9fb2fbd9331496
GitHub pull request Patch Available

Fix REST path traversal token-redaction bypass (GHSA-hxpf-9xvq-wph8)

Patch available: Labs64/NetLicensing-MCP 0.1.8 (PR #6 merged 2026-06-18)

https://github.com/Labs64/NetLicensing-MCP/pull/6
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

REST Path Traversal Bypasses Token Redaction in netlicensing-mcp · Advisory · Labs64/NetLicensing-MCP · GitHub

https://github.com/Labs64/NetLicensing-MCP/security/advisories/GHSA-hxpf-9xvq-wph8

Vendor Advisories for CVE-2026-57496(1)

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

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
netlicensing-mcp0.0.6 ... 0.1.7 (9 versions)
  • every version up to 0.1.8: fixed in 0.1.8
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 17× in last 7d / 32× 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-27 16:32 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  2. 2026-10-27 08:54 UTCEG score recompute
  3. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  4. 2026-10-26 06:26 UTCEG score recompute
  5. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  6. 2026-10-25 14:17 UTCEG score recompute
  7. 2026-10-25 05:27 UTCEG score recompute
  8. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  9. 2026-10-24 04:27 UTCEG score recompute
  10. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  11. 2026-10-23 03:27 UTCEG score recompute
  12. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  13. 2026-10-22 02:27 UTCEG score recompute
  14. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  15. 2026-10-21 01:25 UTCEG score recompute
  16. 2026-10-21 01:18 UTCEG score recompute
  17. 2026-10-21 00:09 UTCEG score recompute
  18. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  19. 2026-10-19 23:08 UTCEG score recompute
  20. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  21. 2026-10-18 22:09 UTCEG score recompute
  22. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  23. 2026-10-18 03:28 UTCEG score recompute
  24. 2026-10-17 21:06 UTCEG score recompute
  25. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.4% · 27th percentile
Show 11 more
  1. 2026-10-16 20:06 UTCEG score recompute
  2. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  3. 2026-10-15 19:28 UTCEG score recompute
  4. 2026-10-12 15:54 UTCEG score recompute
  5. 2026-10-11 19:37 UTCEG score recompute
  6. 2026-10-11 16:52 UTCEG score recompute
  7. 2026-10-11 14:15 UTCEG score recompute
  8. 2026-07-30 22:27 UTCEG score recompute
  9. 2026-07-26 17:20 UTCEG score recompute
  10. 2026-07-23 03:20 UTCEG score recompute
  11. 2026-07-21 13:48 UTCEG score recompute

Related CVEs(same product + same CWE)

Same product

1 shown

PyPI:netlicensing-mcp

Frequently asked(5)

What is CVE-2026-57496?
CVE-2026-57496 is a critical-severity vulnerability; its CVE record was published on June 18, 2026. NetLicensing MCP Server is a natural-language interface that enables agentic applications to manage the software-licensing lifecycle in Labs64 NetLicensing. Prior to 0.1.8, netlicensinggetproduct passes the caller-controlled productnumber to src/netlicensingmcp/tools/products.py, which interpolates…
When was the CVE record for CVE-2026-57496 published?
The CVE record for CVE-2026-57496 was published on June 18, 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 October 21, 2026; the record at its source may have been updated since.
Is CVE-2026-57496 actively exploited?
CVE-2026-57496 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (37th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-57496?
CVE-2026-57496 has a CVSS base score of 9.6 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-57496?
A fix for CVE-2026-57496 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-57496 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-57496

Explore →

Is Your Infrastructure Affected by CVE-2026-57496?

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

Book a Demo →Browse All CVEs