Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Low, CVSS 2.9

libsql-sqlite3-parser crash due to invalid UTF-8 input

CVE-2025-47736GHSA-8m95-fffc-h4c5

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • crates.io libsql-sqlite3-parser

    Affected
    <= 0.13.0
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
2.9 · CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L
EPSS
  • CVE-2025-47736: 0.26% estimated exploitation activity in the next 30 days; percentile 17.45 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

dialect/mod.rs in the libsql-sqlite3-parser crate through 0.13.0 before 14f422a for Rust can crash if the input is not valid UTF-8.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-8m95-fffc-h4c5

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-47736

Advisory: libsql-sqlite3-parser crash due to invalid UTF-8 input
IDs: CVE-2025-47736, GHSA-8m95-fffc-h4c5
Record: https://patchnext.com/advisories/cve-2025-47736 (revision 1, source checked 26 Oct 2026, 15:38 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 2.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io libsql-sqlite3-parser: affected <= 0.13.0

## Suggested inspection (read-only)
- crates.io libsql-sqlite3-parser: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on libsql-sqlite3-parser.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-8m95-fffc-h4c5 (GitHub-reviewed advisory GHSA-8m95-fffc-h4c5 lists affected ranges: crates.io libsql-sqlite3-parser >=0 <=0.13.0)

Commands are suggestions: review each one before running it.

Loading voting…