Which versions of rocksdb are affected by GHSA-XPP3-XRFF-W6RH?

rocksdb (rust) versions < 0.19.0 is affected.

Is there a fix for GHSA-XPP3-XRFF-W6RH?

Yes. GHSA-XPP3-XRFF-W6RH is fixed in 0.19.0. Upgrade to this version or later.

Is GHSA-XPP3-XRFF-W6RH exploitable, and should I be worried?

Whether GHSA-XPP3-XRFF-W6RH is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether GHSA-XPP3-XRFF-W6RH is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

GHSA-XPP3-XRFF-W6RH in rocksdb

Q: What is GHSA-XPP3-XRFF-W6RH?

GHSA-XPP3-XRFF-W6RH is a medium-severity security vulnerability in rocksdb (rust), affecting versions < 0.19.0. It is fixed in 0.19.0.

Q: Is there a fix for GHSA-XPP3-XRFF-W6RH?

Yes. GHSA-XPP3-XRFF-W6RH is fixed in 0.19.0. Upgrade to this version or later.

Q: Is GHSA-XPP3-XRFF-W6RH exploitable, and should I be worried?

Whether GHSA-XPP3-XRFF-W6RH is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether GHSA-XPP3-XRFF-W6RH is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix GHSA-XPP3-XRFF-W6RH?

Upgrade rocksdb to 0.19.0 or later.

GHSA-XPP3-XRFF-W6RH

GHSA-XPP3-XRFF-W6RH is a medium-severity security vulnerability in rocksdb (rust), affecting versions < 0.19.0. It is fixed in 0.19.0.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!

Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

rocksdb vulnerable to out-of-bounds read

Affected versions of this crate called the RocksDB C API
rocksdb_open_column_families_with_ttl() with a pointer to a single integer
TTL value, but one TTL value for each column family is expected.

This is only relevant when using
rocksdb::DBWithThreadMode::open_cf_descriptors_with_ttl() with multiple
column families.

This bug has been fixed in v0.19.0.

Impact

Affected versions

rocksdb (< 0.19.0)

Security releases

rocksdb → 0.19.0 (rust)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade rocksdb to 0.19.0 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is GHSA-XPP3-XRFF-W6RH? GHSA-XPP3-XRFF-W6RH is a medium-severity security vulnerability in rocksdb (rust), affecting versions < 0.19.0. It is fixed in 0.19.0.
Which versions of rocksdb are affected by GHSA-XPP3-XRFF-W6RH? rocksdb (rust) versions < 0.19.0 is affected.
Is there a fix for GHSA-XPP3-XRFF-W6RH? Yes. GHSA-XPP3-XRFF-W6RH is fixed in 0.19.0. Upgrade to this version or later.
Is GHSA-XPP3-XRFF-W6RH exploitable, and should I be worried? Whether GHSA-XPP3-XRFF-W6RH is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether GHSA-XPP3-XRFF-W6RH is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix GHSA-XPP3-XRFF-W6RH? Upgrade rocksdb to 0.19.0 or later.