What is GHSA-MGVV-5MXP-XQ67?

GHSA-MGVV-5MXP-XQ67 is a low-severity security vulnerability in sqlite3 (rubygems), affecting versions = 1.5.0. It is fixed in 1.5.1.

Which versions of sqlite3 are affected by GHSA-MGVV-5MXP-XQ67?

sqlite3 (rubygems) versions = 1.5.0 is affected.

Is there a fix for GHSA-MGVV-5MXP-XQ67?

Yes. GHSA-MGVV-5MXP-XQ67 is fixed in 1.5.1. Upgrade to this version or later.

Is GHSA-MGVV-5MXP-XQ67 exploitable, and should I be worried?

Whether GHSA-MGVV-5MXP-XQ67 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-MGVV-5MXP-XQ67 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-MGVV-5MXP-XQ67 in sqlite3

Q: How do I fix GHSA-MGVV-5MXP-XQ67?

Upgrade sqlite3 to 1.5.1 or later.

Summary

SQLite3 addresses vulnerability in packaged version of libsqlite

The rubygem sqlite3 v1.5.1 upgrades the packaged version of libsqlite from v3.39.3 to v3.39.4.

libsqlite v3.39.4 addresses a vulnerability described as follows in the release notification:

Version 3.39.4 is a minimal patch against the prior release that addresses issues found since the
prior release. In particular, a potential vulnerability in the FTS3 extension has been fixed, so
this should be considered a security update.

In order to exploit the vulnerability, an attacker must have full SQL access and must be able to
construct a corrupt database with over 2GB of FTS3 content. The problem arises from a 32-bit
signed integer overflow.

This vulnerability has not been assigned a CVE and does not have a severity declared.

Please note that this advisory only applies to the sqlite3 gem v1.5.0, and only if the packaged libsqlite is being used. If you've overridden defaults at installation time to use system libraries instead of packaged libraries, you should instead pay attention to your distro's libsqlite release announcements.

Mitigation

Upgrade to the rubygem sqlite3 v1.5.1 or later.

Users who are unable to upgrade the sqlite3 gem may also choose a more complicated mitigation: compile and link sqlite3 against external libsqlite >= 3.39.4 which will also address these same issues.

References

Upstream release notes: https://sqlite.org/releaselog/3_39_4.html
Instructions for compiling against system libraries: https://github.com/sparklemotion/sqlite3-ruby

Impact

Affected versions

sqlite3 (= 1.5.0)

Security releases

sqlite3 → 1.5.1 (rubygems)

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 sqlite3 to 1.5.1 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-MGVV-5MXP-XQ67? GHSA-MGVV-5MXP-XQ67 is a low-severity security vulnerability in sqlite3 (rubygems), affecting versions = 1.5.0. It is fixed in 1.5.1.
Which versions of sqlite3 are affected by GHSA-MGVV-5MXP-XQ67? sqlite3 (rubygems) versions = 1.5.0 is affected.
Is there a fix for GHSA-MGVV-5MXP-XQ67? Yes. GHSA-MGVV-5MXP-XQ67 is fixed in 1.5.1. Upgrade to this version or later.
Is GHSA-MGVV-5MXP-XQ67 exploitable, and should I be worried? Whether GHSA-MGVV-5MXP-XQ67 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-MGVV-5MXP-XQ67 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-MGVV-5MXP-XQ67? Upgrade sqlite3 to 1.5.1 or later.