CVE-2026-70003 json
JDBC Driver for SQL Server Security Feature Bypass Vulnerability
published yesterday modified 17h ago also EUVD-2026-122075
- cvss
- 8.7
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 23%
- public exploits
- 0
- none known
Summary
Improper verification of cryptographic signature in JDBC Driver for SQL Server allows an unauthorized attacker to bypass a security feature over a network.
Patch / fix
- Microsoft Microsoft JDBC Driver for SQL Server 13.4 13.6.0
Is CVE-2026-70003 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 23h ago
Exploit prediction
0.30% chance of exploitation in the next 30 days, higher than 23% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.7 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N/E:U/RL:O/RC:C |
| CNA | 3.1 | 8.7 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N |
Affected products
- Microsoft Microsoft JDBC Driver for SQL Server 13.4
Classification
- Weakness
-
- CWE-347 Improper Verification of Cryptographic Signature
References
-
msrc.microsoft.com
/update-guide/vulnerability/CVE-2026-70003
vendor-advisory, patch
Sources
- CVE List CVE-2026-70003
- NVD CVE-2026-70003
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.