Skip to main content
VulnerabilityPublished Updated

CVE-2026-23838: NixOS nixpkgs · Insertion of Sensitive Information into Externally-Accessible File or Directory

Affects NixOS nixpkgsSource CVE Database V5

0

Not known to be exploited · CVSS 8.7 High : upgrade to 26.05 soon.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 43% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 26.05
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Jan 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: 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 26 Oct 2026.

What to do

Upgrade NixOS nixpkgs to 26.05.

Affected software

ProductAffectedFixed in
NixOSnixpkgsAffected
  • >=23.05 <26.05
Fixed in
  • 26.05

AI-suggested

European organizations should immediately audit their Tandoor Recipes installations on NixOS to determine if they are running affected versions (>=23.05 and <26.05) with default MEDIA_ROOT configurations. The primary mitigation is to move MEDIA_ROOT into a dedicated subdirectory within /var/lib/tandoor-recipes or another non-web-accessible location to separate media files from the database file. This prevents direct HTTP access to db.sqlite3. Alternatively, migrating from SQLite to PostgreSQL or another database backend that does not store data in a web-accessible directory is recommended for enhanced security. Web server configurations (e.g., nginx) should be reviewed and updated to explicitly deny access to the database file (db.sqlite3) by adding location blocks or access control rules. For deployments using Gunicorn with GUNICORN_MEDIA=1, disable this setting or ensure MEDIA_ROOT is not the same directory as the database. Organizations should upgrade to NixOS 26.05 or later, which changes the default MEDIA_ROOT to a safer subdirectory, but must verify that system.stateVersion is set accordingly to benefit from this fix. Regular backups and monitoring for unusual access patterns to media directories are advised. Finally, organizations should review their incident response plans to address potential data exposure and ensure compliance with GDPR notification requirements if a breach is suspected.

Description

Tandoor Recipes is a recipe manager than can be installed with the Nix package manager. Starting in version 23.05 and prior to version 26.05, when using the default configuration of Tandoor Recipes, specifically using SQLite and default `MEDIA_ROOT`, the full database file may be externally accessible, potentially on the Internet. The root cause is that the NixOS module configures the working directory of Tandoor Recipes, as well as the value of `MEDIA_ROOT`, to be `/var/lib/tandoor-recipes`. This causes Tandoor Recipes to create its `db.sqlite3` database file in the same directory as `MEDIA_ROOT` causing it to be accessible without authentication through HTTP like any other media file. This is the case when using `GUNICORN_MEDIA=1` or when using a web server like nginx to serve media files. NixOS 26.05 changes the default value of `MEDIA_ROOT` to a sub folder of the data directory. This only applies to configurations with `system.stateVersion` >= 26.05. For older configurations, one of the workarounds should be applied instead. NixOS 25.11 has received a backport of this patch, though it doesn't fix this vulnerability without user intervention. A recommended workaround is to move `MEDIA_ROOT` into a subdirectory. Non-recommended workarounds include switching to PostgreSQL or disallowing access to `db.sqlite3`.

References

Community reviews

Loading reviews…