Skip to content

← Actionable
Critical, CVSS 9.6amended

netlicensing-mcp: REST Path Traversal Bypasses Token Redaction

CVE-2026-57496GHSA-hxpf-9xvq-wph8

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (netlicensing-mcp 0.1.8), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
9.6 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N
EPSS
  • CVE-2026-57496: 0.43% estimated exploitation activity in the next 30 days; percentile 37.86 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary The netlicensinggetproduct MCP tool in netlicensing-mcp interpolates a caller-controlled productnumber argument directly into a REST URL path without any validation. Passing ../token as the product number causes httpx to normalize /product/../token into /token, silently redirecting the request to the NetLicensing token endpoint instead of the intended product endpoint. The response is then serialized through the generic wrapjson wrapper rather than the token-specific wrapjsontokenread wrapper, bypassing all APIKEY number and SHOP shopURL redaction. An authenticated MCP client can recover plaintext API key values that the token read tools intentionally mask, including admin-level APIKEY credentials. Details The vulnerability is a path traversal (CWE-22) that exploits the interaction between unsanitized string interpolation and httpx's WHATWG URL normalization. Source — src/netlicensingmcp/tools/products.py:22 productnumber is inserted directly into the REST path with no…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-hxpf-9xvq-wph8

  2. Revision 2 · amended ·

    Amended from osv record GHSA-hxpf-9xvq-wph8

  3. Revision 1 · created ·

    Published from ghsa record GHSA-hxpf-9xvq-wph8

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-57496

Advisory: netlicensing-mcp: REST Path Traversal Bypasses Token Redaction
IDs: CVE-2026-57496, GHSA-hxpf-9xvq-wph8
Record: https://patchnext.com/advisories/cve-2026-57496 (revision 3, source checked 26 Oct 2026, 13:55 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.6)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: netlicensing-mcp 0.1.8. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI netlicensing-mcp: affected < 0.1.8; fixed in 0.1.8

## Suggested inspection (read-only)
- `python -m pip show netlicensing-mcp`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on netlicensing-mcp.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-hxpf-9xvq-wph8 (GitHub-reviewed advisory GHSA-hxpf-9xvq-wph8 lists affected ranges: PyPI netlicensing-mcp >=0 <0.1.8)
- Verified: https://osv.dev/vulnerability/GHSA-hxpf-9xvq-wph8 (OSV record GHSA-hxpf-9xvq-wph8 lists affected ranges: PyPI netlicensing-mcp >=0 <0.1.8 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…