CVE-2026-75513

CRITICALPre-NVD 9.19.1—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5%, top 62% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.1Exploit: Elevated riskExposed: 0

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

Marten is a .NET Transactional Document DB and Event Store on PostgreSQL. From version 7.0.0 until 9.13.0, several Marten LINQ and tenant-management paths interpolate runtime, potentially attacker-controlled strings into single-quoted SQL literals without escaping or parameterization. The primary confirmed vector is a dictionary indexer key used by Where filters in src/Marten/Linq/Members/Dictionaries/DictionaryItemMember.cs. Additional affected sinks include SelectParser.cs, DatabaseScopedTenantPartitions.cs, and DeleteAllForTenant.cs reached through IEventStore.DeleteProjectionProgressAsync, while DictionaryContainsKeyFilter.cs (Newtonsoft serializer only; System.Text.Json is not affected) handles ContainsKey calls. Events/Daemon/Internals/EventLoader.cs contains a related per-tenant partition-pruning literal that the advisory identifies as a defense-in-depth sink. A crafted single quote can escape the generated literal, enabling filter or multi-tenant authorization bypass and blind data exfiltration, and deployments that permit semicolon-batched Npgsql statements may also allow data modification. This issue is fixed in version 9.13.0.

CVSS v3
9.1
EG Score
9.1(medium)
EG Risk
57(Track)
EG Risk 57/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity91% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
38%
KEV
Not listed

Published

September 16, 2026

Last Modified

September 19, 2026

Advisory Details (4)

Auto-updated Sep 16, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_release, github, github_pr.
github_release Patch Available

Marten 9.13.0

Patch available: JasperFx/marten 9.13.0

https://github.com/JasperFx/marten/releases/tag/9.13.0
github_commit Patch Available

commit 61882d042485 (JasperFx/marten)

Patch available: JasperFx/marten V9.18.0 (contains commit 61882d042485)

https://github.com/JasperFx/marten/commit/61882d0424854cb48703f08bdb246894ac576bed
github_pr Patch Available

Fix SQL injection in LINQ provider via unescaped string literals

Patch available: JasperFx/marten V9.18.0 (PR #4911 merged 2026-07-08)

https://github.com/JasperFx/marten/pull/4911
github Patch Available🟡 PoC Available

SQL injection in Marten's LINQ provider via unescaped string literals · Advisory · JasperFx/marten · GitHub

https://github.com/JasperFx/marten/security/advisories/GHSA-rfx3-98h7-v3xp

Vendor Advisories for CVE-2026-75513(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)
NuGet(1)
PackageVulnerable rangeFixed inDependents
Marten7.0.0 ... 9.9.1 (207 versions)9.13.0—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 15× in last 7d / 19× 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-09-24 15:55 UTCEG score recompute
  2. 2026-09-24 14:04 UTCEPSS rescore
  3. 2026-09-23 19:41 UTCEG score recompute
  4. 2026-09-23 17:54 UTCEPSS rescore
  5. 2026-09-22 19:32 UTCEG score recompute
  6. 2026-09-22 16:01 UTCEPSS rescore
  7. 2026-09-21 23:23 UTCEG score recompute
  8. 2026-09-21 21:09 UTCEPSS rescore
  9. 2026-09-20 23:03 UTCEG score recompute
  10. 2026-09-20 20:16 UTCEPSS rescore
  11. 2026-09-19 18:46 UTCEG score recompute
  12. 2026-09-19 02:29 UTCEG score recompute
  13. 2026-09-19 02:01 UTCEG score recompute
  14. 2026-09-18 22:35 UTCEG score recompute
  15. 2026-09-18 19:28 UTCEPSS rescore
  16. 2026-09-17 22:20 UTCEG score recompute
  17. 2026-09-16 21:23 UTCEG score recompute
  18. 2026-09-16 20:52 UTCEG score recompute
  19. 2026-09-16 20:49 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Same product

1 shown

NuGet:Marten

Frequently asked(5)

What is CVE-2026-75513?
CVE-2026-75513 is a critical vulnerability published on September 16, 2026. Marten is a .NET Transactional Document DB and Event Store on PostgreSQL. From version 7.0.0 until 9.13.0, several Marten LINQ and tenant-management paths interpolate runtime, potentially attacker-controlled strings into single-quoted SQL literals without escaping or parameterization. The primary…
When was CVE-2026-75513 disclosed?
CVE-2026-75513 was first published in the National Vulnerability Database on September 16, 2026, with the most recent update on September 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-75513 actively exploited?
CVE-2026-75513 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 62.2% of all scored CVEs.
What is the CVSS score of CVE-2026-75513?
CVE-2026-75513 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-75513?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-75513, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-75513

Explore →

Is Your Infrastructure Affected by CVE-2026-75513?

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

Book a Demo →Browse All CVEs