CVE-2026-15526

LOWPre-NVD 3.33.3
EchelonGraph scoreHIGH confidence

Score 3.3 from GitHub Security Advisory (severity: LOW) published 2026-07-13. a secondary CVSS source baseline 3.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 sources updated this weekElevated
3.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 3.3Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

A flaw has been found in augmnt augments-mcp-server 7.1.0. This issue affects the function scanProjectDeps of the file src/tools/v4/scan-project-deps.ts of the component scan_project_deps. Executing a manipulation of the argument packageJsonPath can lead to path traversal. The attack can only be executed locally. The exploit has been published and may be used. The project was informed of the problem early through an issue report but has not responded yet.

CVSS v3
3.3
EG Score
3.3(high)
EPSS
3.5%
KEV
Not listed

Published

July 13, 2026

Last Modified

July 13, 2026

Vendor Advisories for CVE-2026-15526(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 10× in last 7d / 10× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-07-16 00:56 UTCEG score recompute
  2. 2026-07-16 00:56 UTCGHSA enrichment
  3. 2026-07-15 16:57 UTCEPSS rescore
  4. 2026-07-15 02:00 UTCEPSS rescore
  5. 2026-07-13 22:30 UTCEPSS rescore
  6. 2026-07-13 18:08 UTCNVD updateCVSS v4 → 1.9
  7. 2026-07-13 16:22 UTCMITRE cvelistV5CVSS v4 → 4.8
  8. 2026-07-13 04:19 UTCNVD updateCVSS v4 → 1.9
  9. 2026-07-13 04:03 UTCEG score recompute
  10. 2026-07-13 04:02 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-15526?
CVE-2026-15526 is a low vulnerability published on July 13, 2026. A flaw has been found in augmnt augments-mcp-server 7.1.0. This issue affects the function scanProjectDeps of the file src/tools/v4/scan-project-deps.ts of the component scanprojectdeps. Executing a manipulation of the argument packageJsonPath can lead to path traversal. The attack can only be…
When was CVE-2026-15526 disclosed?
CVE-2026-15526 was first published in the National Vulnerability Database on July 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-15526 actively exploited?
CVE-2026-15526 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-15526?
CVE-2026-15526 has a CVSS v3 base score of 3.3 (NVD).
How do I remediate CVE-2026-15526?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-15526, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-15526?

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