Read the docs
TI-2022-22211 Aliases CVE-2022-45136GHSA-g2qw-6vrr-v6pq

Apache Jena SDB allows arbitrary deserialisation via JDBC

Priority MEDIUM 52CWE-502Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
Low
Impact type
Code execution
Confidentiality · integrity · availability
High · High · High
Fix status
No fix listed

Attack profile from CVSS 3.1 · CISA ADP. Fix status from CNA and GitHub. Impact type from CWE-502.

Summary

Apache Jena SDB 3.17.0 and earlier is vulnerable to a JDBC Deserialisation attack if the attacker is able to control the JDBC URL used or cause the underlying database server to return malicious data. The mySQL JDBC driver in particular is known to be vulnerable to this class of attack. As a result an application using Apache Jena SDB can be subject to RCE when connected to a malicious database server. Apache Jena SDB has been EOL since December 2020 and users should migrate to alternative options e.g. Apache Jena TDB 2.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.01658 76th percentileScored 2026-11-07
Fix No fix listed No fixed version in the sources yet

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
Yes
Technical impact
Total

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
ApacheApache Jena SDBup to 3.17.0—No fix listedCNA
—org.apache.jena:jena-sdb (Maven)up to 3.17.0—No fix listedGHSA-g2qw-6vrr-v6pq
  • Apache Jena SDB VendorApache Affected up to 3.17.0 Fixed in — No fix listed CNA
  • org.apache.jena:jena-sdb (Maven) Vendor— Affected up to 3.17.0 Fixed in — No fix listed GHSA-g2qw-6vrr-v6pq

CPE configurations NVD · 1

CPEVersionsRoleVendor
cpe:2.3:a:apache:jena_sdb:*:*:*:*:*:*:*:*up to 3.17.0VulnerableApache
  • cpe:2.3:a:apache:jena_sdb:*:*:*:*:*:*:*:* Versions up to 3.17.0 Vulnerable ·Apache

Remediation

No fixed version listed by the sources yet.

Timeline

  1. 2026-10-02 Threatist record created from CVE-2022-45136
  2. 2026-10-03 Alias added: GHSA-g2qw-6vrr-v6pq

References

Sources