Skip to main content
Menu
CVEs

CVE

littlefs out-of-bounds reads in lfs_dir_traverse during migration

CVE-2026-129490EUVD-2026-126101GHSA-Q985-5V39-R948

CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

6.8MediumCNA
Exploited
No known exploitation
Fix
No fix listed
Who is exposed
Not reported
Published
Last modified
Reference
Last checked
0.17% · 5th percentile
12/100 · provisional
None on Exploit-DB, Metasploit or GitHub

Summary

A local attacker, without needing to log in, can supply a crafted littlefs v1 image that a user then migrates, causing out-of-bounds stack reads that crash the process. The flaw is a type confusion in lfs_dir_traverse() in littlefs builds that use LFS_MIGRATE.

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

Original description

littlefs through 2.11.3, when built with LFS_MIGRATE, contains a type confusion vulnerability in lfs_dir_traverse() that treats a stack lfs_diskoff struct as an lfs_attr array. Attackers can supply a crafted littlefs v1 image whose metadata is read as LFS_FROM_USERATTRS during migration, causing out-of-bounds stack reads and process crashes.

cve.now Index

12Pcve.now Index 12 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure?/25Unknown. No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity6.8/10CVSS 6.8
  • No patch5/5No patch listed yet

What would change the score

  • Would score about 67 if added to CISA KEV
  • Would score about 62 if CISA's SSVC rates exploitation active
  • Would score about 34 if advisories confirm default setups are exposed

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-129490 (littlefs through 2.11.3 Type Confusion in lfs_dir_traverse via lfs_migrate), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-129490 (entry last updated 2026-11-16):
Affected:
- littlefs-project littlefs: through 2.11.3
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-129490 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129490 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/littlefs-project/littlefs/issues/1213
- https://github.com/littlefs-project/littlefs/blob/v2.11.3/lfs.c#L1056-L1063
- https://www.vulncheck.com/advisories/littlefs-through-2.11.3-type-confusion-in-lfs-dir-traverse-via-lfs-migrate
- http://www.openwall.com/lists/oss-security/2026/11/16/6
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-129490
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-129490"}.

Timeline

  1. CVE published
  2. First seen by cve.now1 day
  3. Record last updated

Affected versions

  • littlefs-project littlefs

    through 2.11.3

Evidence 7

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Public exploit code · 1

Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).

  1. Exploit

Write-ups · 1

Establishes: Technical detail and context.

  1. Link

Other links · 3

  1. Report
  2. Repository
  3. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-129490

Is CVE-2026-129490 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-129490?

littlefs: through 2.11.3.Source: cve.now feed data