Skip to main content
CVE-2026-126302VulnerabilityPublished

safety · NLTK: Symlink escape

Affects safetySource GCVE Database

0
Compare
Authoritative record:CVE-2026-126302· Medium 4.8

Not known to be exploited · CVSS 4.8 Medium : upgrade to 3.8.1_3 when convenient.

Data as of 17 Nov 2026, 19:34 UTC

CVSS 4.0 base score
4.8Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.04.8
CNA (VulnCheck)CVSS 3.13.3
Patch
Available – fixed in 3.8.1_3
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.

What to do

Upgrade safety to 3.8.1_3.

Affected software

ProductAffectedFixed in
Homebrewsafetypkg:brew/safetyOther threatsAffected
  • >=3.7.0_7 <3.8.1_3
Fixed in
  • 3.8.1_3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available in NLTK version 3.8.1_3 that enforces path containment checks in sql_query(), preventing symlink escape. Users should upgrade to this fixed version to mitigate the vulnerability. Until patched, avoid running sql_query() on untrusted data roots or ensure that only trusted users have write access to NLTK data root directories. No other specific mitigations are indicated.

Description

The NLTK library's sql_query() function in the chat80 module bypasses the pathsec sandbox intended to restrict SQLite database access to specific data roots. It does so by following symbolic links inside trusted data roots that point to SQLite databases outside those roots, allowing read access to out-of-sandbox databases. This occurs because sql_query() uses nltk.data.find() which only performs lexical checks and does not resolve symlinks, unlike other functions that enforce path containment. An attacker with write access to a trusted NLTK data root can exploit this to read sensitive SQLite databases elsewhere on the filesystem.

References

Community reviews

Loading reviews…