Microsoft JDBC Driver is widely used in enterprise Java apps; signature-bypass can allow tampered driver acceptance leading to RCE or unauthorized access across many organizations.
CVE-2026-70003
Signature verification bypass in Microsoft JDBC Driver for SQL Server.
Is CVE-2026-70003 being exploited?
Not confirmed. CVE-2026-70003 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.30% probability of exploitation in the next 30 days.
How severe is CVE-2026-70003?
CVE-2026-70003 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-70003?
Yes. A fix has been recorded for CVE-2026-70003. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-70003 affect?
CVE-2026-70003 affects Microsoft JDBC Driver for SQL Server, Java applications using the JDBC driver, Servers/clients connecting to SQL Server via the driver. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-70003?
Apply vendor update ASAP; restrict DB client access and validate driver binaries.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote attacker can bypass signature verification to load tampered/malicious driver, potentially enabling remote code execution or unauthorized access in client apps.
Immediate action required
- affected>= 1.0.0 and < 13.6.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
cisa ssvc
- exploitation
- none
- automatable
- no
- technical impact
- total
Assessed by CISA 11 Nov 2026 (SSVC 2.0.3).
timeline
- 10 Nov 2026Published
- 11 Nov 2026CISA SSVC assessment: exploitation none · 1 day later
- 11 Nov 2026CVE record last updated · same day later
- 12 Nov 2026Analysed by vulneraibility.com · 1 day later
- Patchmsrc.microsoft.com /update-guide/vulnerability/CVE-2026-70003
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.