# CVE-2026-128241: libexpat xmlwf through 2.10.0 Symlink Following via -d Output Directory


- **Severity:** Medium 4.1 (`CVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:P/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 13 Nov 2026
- **Updated:** 17 Nov 2026
- **Also known as:** AZL-113822, DEBIAN-CVE-2026-128241, ECHO-2326-3d45-30aa, GHSA-2qp8-23fp-hmf7, UBUNTU-CVE-2026-128241

## What is CVE-2026-128241?

CVE-2026-128241 is a medium-severity vulnerability in libexpat, published on 13 Nov 2026. 

### Official description

The xmlwf tool in libexpat through 2.10.0 contains a symlink following vulnerability because -d output mode opens files with fopen("wb"), which follows symbolic links. Local attackers with write access to the output directory can plant a symlink at the expected output name to truncate or overwrite files writable by the xmlwf user.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

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

1 open source package ship an affected version, including libexpat/libexpat.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `libexpat/libexpat` | GitHub | `pkg:github/libexpat/libexpat` | All versions to 2.10.0 | None |

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

Upgrade to a fixed version.

## Is CVE-2026-128241 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-128241 is a medium-severity vulnerability in libexpat, published on 13 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-128241 in the wild and no public exploit code.

Affected packages and fixed versions:
- libexpat/libexpat (GitHub): affected all versions up to 2.10.0; 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.
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-128241/ (Markdown: https://insights.sbomify.com/CVE-2026-128241/index.md)
```

## Sources

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

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