# CVE-2026-129490: littlefs through 2.11.3 Type Confusion in lfs_dir_traverse via lfs_migrate

> A crafted littlefs v1 image can crash processes during LFS_MIGRATE via type confusion in littlefs.

- **Severity:** Medium 6.8 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Harmful if only installed:** No
- **Needs a specific call:** Yes (`lfs_dir_traverse`, `lfs_migrate`)
- **Fix available:** No
- **Published:** 15 Nov 2026
- **Updated:** 16 Nov 2026
- **Also known as:** GHSA-q985-5v39-r948, UBUNTU-CVE-2026-129490

## What is CVE-2026-129490?

CVE-2026-129490 is a medium-severity memory corruption vulnerability in littlefs-project littlefs, published on 15 Nov 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

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

Weakness: CWE-843 (Access of Resource Using Incompatible Type)

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

1 open source package ship an affected version, including littlefs-project/littlefs.

An affected version is only exploitable if your software calls lfs_dir_traverse or lfs_migrate. Many projects that include it are not exposed.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `littlefs-project/littlefs` | GitHub | `pkg:github/littlefs-project/littlefs` | All versions to 2.11.3 | None |

## How do I fix CVE-2026-129490?

No fix has been published for CVE-2026-129490 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-129490 being exploited?

There is no known exploitation of CVE-2026-129490 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-129490 and fix it if it is affected.

What it is: CVE-2026-129490 is a medium-severity memory corruption vulnerability in littlefs-project littlefs, published on 15 Nov 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-129490 in the wild and no public exploit code.
Exposure: An affected version is only exploitable if your software calls lfs_dir_traverse or lfs_migrate. Many projects that include it are not exposed.

Affected packages and fixed versions:
- littlefs-project/littlefs (GitHub): affected all versions up to 2.11.3; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
   If an affected version is present, also search the code for calls to lfs_dir_traverse or lfs_migrate and report whether any exist.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-129490/ (Markdown: https://insights.sbomify.com/CVE-2026-129490/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-129490
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-129490
- OSV: https://osv.dev/vulnerability/CVE-2026-129490

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-129490/
Summaries are generated and may contain mistakes; the official description above is the record.
