cve.bz

CVE-2026-70003 JDBC Driver for SQL Server Security Feature Bypass Vulnerability

8.7 highEPSS 0.3%

High (8.7) in microsoft microsoft jdbc driver for sql server 13.4. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.

On this page
Improper verification of cryptographic signature in JDBC Driver for SQL Server allows an unauthorized attacker to bypass a security feature over a network.

Severity

CVSS 3.1

8.7 high
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N
EPSS
0.3% estimated probability of exploitation activity in the next 30 days; 23rd percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-11-11. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-347 Improper Verification of Cryptographic Signature
OWASP Top 10
A04:2025 Cryptographic Failures
Published
Modified
Assigned by
microsoft (CNA)
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-70003 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-70003?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-70003?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-70003 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-70003

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-70003](https://cve.bz/cve/badge/CVE-2026-70003.svg)](https://cve.bz/cve/CVE-2026-70003)

HTML:

<a href="https://cve.bz/cve/CVE-2026-70003"><img src="https://cve.bz/cve/badge/CVE-2026-70003.svg" alt="CVE-2026-70003"></a>

Affected

  • microsoft:microsoft jdbc driver for sql server 13.4

Versions

From the CNA's record in the CVE List.

ProductAffected
Microsoft JDBC Driver for SQL Server 13.4from 1.0.0 before 13.6.0

Attack patterns (CAPEC)

  • CAPEC-463 Padding Oracle Crypto Attack Severity: High
  • CAPEC-475 Signature Spoofing by Improper Validation Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON