# CVE-2026-131871: WLA DX 9.7 through 10.7 Stack Buffer Overflow via wlalink parse_data_blocks()


- **Severity:** High 8.5 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 18 Nov 2026
- **Updated:** 18 Nov 2026
- **Also known as:** GHSA-hq2x-hr3f-5jm7

## What is CVE-2026-131871?

CVE-2026-131871 is a high-severity vulnerability in Ville Helin WLA DX, published on 18 Nov 2026. 

### Official description

WLA DX 9.7 through 10.7 contains a stack-based buffer overflow vulnerability in parse_data_blocks() in wlalink/analyze.c that copies section namespaces without length checks. Attackers can supply a crafted object or library file with a namespace longer than 255 bytes or unterminated to overflow the 256-byte stack buffer when linked.

Weakness: CWE-121 (Stack-based Buffer Overflow)

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

1 open source package ship an affected version, including vhelin/wla-dx.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `vhelin/wla-dx` | GitHub | `pkg:github/vhelin/wla-dx` | From 9.7 to 10.7 | None |

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

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

## Is CVE-2026-131871 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-131871 is a high-severity vulnerability in Ville Helin WLA DX, published on 18 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-131871 in the wild and no public exploit code.

Affected packages and fixed versions:
- vhelin/wla-dx (GitHub): affected from 9.7 up to 10.7; 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-131871/ (Markdown: https://insights.sbomify.com/CVE-2026-131871/index.md)
```

## Sources

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

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