CVE Intelligence
High Memory corruption exploit reference

CVE-2023-7104 — SQLite SQLite3 make alltest sqlite3session.c sessionReadRecord heap-based overflow

A vulnerability was found in SQLite SQLite3 up to 3.43.0 and classified as critical. This issue affects the function sessionReadRecord of the file ext/session/sqlite3session.c of the component make alltest Handler. The manipulation leads to heap-based buffer overflow. It is recommended to apply a patch to fix this issue. The associated identifier of this vulnerability is VDB-248999.

Published Dec 29, 2023 · Updated Oct 14, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: VulDB

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 1.2% (30-day exploitation probability)+10
  • Technical severity (high)+6
  • CISA SSVC: exploitation "poc"+5

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
1.25%
ahead of 69% of scored CVEs · Oct 14, 2026
Affects
Fedoraproject
Fedora and 2 more
CVSS base
7.3
High · 4 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
Proof of concept
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Partial
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

  • Documented patch — sqlite.org (NIST National Vulnerability Database)

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Fedoraproject Fedora, Sqlite Sqlite, Sqlite SQLite3).
  2. The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
  3. Apply the fixed version or the patch documented under Remediation.
  4. Search available logs for exploit probes matching the vulnerability class (memory corruption), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Fedoraproject Fedora version 39version 38 Vulnerable NIST National Vulnerability Database
Sqlite Sqlite ≤ 3.43.0 Vulnerable NIST National Vulnerability Database
Sqlite SQLite3 version 3.22version 3.43version 3.23version 3.24version 3.25version 3.26version 3.27version 3.28
and 36 more version 3.29version 3.30version 3.31version 3.32version 3.33version 3.34version 3.35version 3.36version 3.37version 3.38version 3.39version 3.40version 3.41version 3.42version 3.10version 3.0version 3.1version 3.2version 3.3version 3.4version 3.5version 3.6version 3.7version 3.8version 3.9version 3.21version 3.11version 3.12version 3.13version 3.14version 3.15version 3.16version 3.17version 3.18version 3.19version 3.20
Vulnerable CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
7.3 CVSS 3.1 High 3.9 3.4 nvd@nist.gov via NIST National Vulnerability Database
5.5 CVSS 3.1 Medium 2.1 3.4 cna@vuldb.com via NIST National Vulnerability Database
5.5 CVSS 3.1 Medium — — GitHub, Inc. via GitHub Security Advisories
5.5 CVSS 3.1 Medium — — VulDB via CVE Program (cve.org) e CISA ADP
5.5 CVSS 3.0 Medium — — VulDB via CVE Program (cve.org) e CISA ADP
5.2 CVSS 2.0 Medium 5.1 6.4 cna@vuldb.com via NIST National Vulnerability Database
5.2 CVSS 2.0 Medium — — VulDB via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L (score shown at the top: nvd@nist.gov)
Scoring entities (NIST, CNA, ADP) score independently; each score is shown with its origin. For prioritization we use 7.3 (NVD (NIST)) as a conservative provisional reference — not a definitive official score.

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-119 · Buffer Errors (Improper Restriction of Operations within Memory Bounds)

Other CVEs with this weakness →

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Correlate service crashes/restarts with inbound traffic; repeated crashes may indicate attempts.
web/proxy/WAF logsnetwork IDS/IPSendpoint telemetry (EDR)crash dumps

Timeline

What happened to this CVE, newest first.

  • 2026
  • Affected products added · sqlite/sqlite3
    Oct 14, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 14, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 14, 2026
  • Fix documented
    Oct 14, 2026 · NIST National Vulnerability Database
  • Affected products added · sqlite/sqlite, fedoraproject/fedora
    Oct 14, 2026 · NIST National Vulnerability Database
  • CVSS changed · 7.3
    Oct 14, 2026 · NIST National Vulnerability Database
  • Source status changed · → Modified
    Oct 14, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 14, 2026 · Alertas do Telegram
  • 2023
  • CVE published
    Dec 29, 2023 · VulDB

Source activity

Repeated readings are counted rather than listed.

  • 2× References added · Oct 14, 2026 – Oct 14, 2026
  • 1× Official description updated · Oct 14, 2026 – Oct 14, 2026

References

17 on the record

Elsewhere on this site

Fedoraproject
every CVE for this vendor
CWE-119
other pages naming this weakness

Related CVEs (same products)

  • High CVE-2026-54230 Abrt: event handler scripts follow symlinks when writing output files, allowing arbitrary file overwrites Jun 13, 2026
  • Medium CVE-2026-54231 Abrt: unsanitized systemd journal content written to dump directory files enables content injection Jun 13, 2026
  • High CVE-2026-11824 SQLite before 3.53.2 Heap Buffer Overflow via FTS5 fts5ChunkIterate Jun 9, 2026
  • High CVE-2026-11822 SQLite before 3.53.2 Memory Corruption in FTS5 Extension Jun 9, 2026
  • High CVE-2026-35093 Libinput: libinput: unauthorized code execution and information disclosure through lua bytecode plugins Apr 1, 2026
  • Medium CVE-2026-35094 Libinput: libinput: information disclosure via dangling pointer in lua plugin handling Apr 1, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2023-7104 is "SQLite SQLite3 make alltest sqlite3session.c sessionReadRecord heap-based overflow", rated High. It affects Fedora (Fedoraproject); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.3 describes technical severity. EPSS 1.25% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.