Skip to content

CVE-2026-11822

Out-of-bounds Read: Is CVE-2026-11822 real, exploitable, or a false positive? Here's the community verdict.

Community verdict: No field verdicts yet. Be the first practitioner to weigh in.

signals

public sources

Exploited in wild
Not listed
CISA KEV
Public exploit
None known
Metasploit/EDB/PoC
Base severity
5.5 Medium
CVSS
Exploitation prob.
0.2%
FIRST EPSS
Weakness
CWE-125 · Out-of-bounds Read
CWE

Moderate signals. Triage by your actual exposure and reachability.

cisa ssvc

CISA Vulnrichment · assessed

Exploitation
None
in the wild
Automatable
No
at scale
Technical impact
Total
on success

CISA decision, by how critical the affected system is to you:

  • low impact → Track
  • medium impact → Track
  • high impact → Track*

Track: normal patch cycle · Track*: watch closely · Attend: patch sooner · Act: patch now. About SSVC ↗

scanner noise

anonymous, aggregated from real reports · via Denoizr
ScannerFlagged inTurned out noise
Wiz1 scan100%

How often this CVE was flagged by each scanner and how much turned out to be noise (false positives), aggregated anonymously from de-noised reports. Higher noise means the alert is more often not a real risk — verify your exposure.

baseline read

auto · not a community verdict

Low signal — verdict needed

Few public signals point to active risk. Whether a scanner hit here is a true or false positive depends on your version and config — community verdicts decide.

Based on CVSS · FIRST EPSS

Confirm or dispute →
Affected:Sqlite

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

SQLite before 3.53.2 contains an out-of-bounds read vulnerability in the FTS5 full-text search extension that allows attackers to crash the process by supplying a crafted database with a malformed FTS5 leaf page. Attackers can set an oversized term length in the leaf page so that fts5LeafSeek() reads past the end of the page buffer while comparing terms during an FTS5 MATCH query, in applications compiled with SQLITE_ENABLE_FTS5.

Published

Embed this verdict
TruePositive verdict for CVE-2026-11822
Markdown
[![TruePositive verdict](https://www.truepositive.app/cve/CVE-2026-11822/badge.svg)](https://www.truepositive.app/cve/CVE-2026-11822)
HTML
<a href="https://www.truepositive.app/cve/CVE-2026-11822"><img src="https://www.truepositive.app/cve/CVE-2026-11822/badge.svg" alt="TruePositive verdict for CVE-2026-11822"></a>

Live badge that updates automatically as the community verdict changes.

timeline

  1. CVSS score changed · 7.8 → 5.5
  2. Published by NVD
  3. CISA SSVC assessment · exploitation: none

Score and exploit changes tracked since .

Community ground truth

Be the first practitioner to weigh in

So far this is only TruePositive's editorial baseline from public sources. Add your real-world verdict below — it becomes the signal the next person triaging this relies on.

🥇 The first 50 practitioners to contribute earn a Founding Contributor badge.

In your experience, is this finding real and exploitable?

awaiting field verdicts
Real, but not a risk here
Not a real issue

Curated baseline: A curated baseline from public sources, shown separately from community verdicts.

No account needed. Anonymous verdicts post as an unverified signal. Log in to make yours verified and earn reputation.

Field notes & remediation

Verdicts are the quick signal. Notes are the evidence and fixes behind them.

  • 0
    Field note · TruePositive EditorialCurated

    This scores high on paper (CVSS 7.8) but the real-world signal is low. It is not in CISA KEV and no public exploit was found, and near-term exploitation looks unlikely (EPSS about 0%). Verify your own exposure before treating it as urgent. It needs local access, so it reads more as a privilege-escalation or post-access risk than a remote one. Not an emergency for most teams, but patch it in your normal cycle and check whether the affected component is actually exposed in your setup.

Add a field note or remediationoptional
Note type

What are you adding?

Markdown supported · minimum 20 characters.

Same weakness: CWE-125 · Out-of-bounds Read.