Skip to main content
Menu
CVEs

CVE

Ville Helin WLA DX stack buffer overflow in wlalink parse_data_blocks()

Affects WLA DX 9.7 through 10.7 when wlalink links a crafted object or library file whose section namespace is longer than 255 bytes or unterminated. The fix is vendor patch 63755ff, as no fixed version is named.

CVE-2026-131871EUVD-2026-128391Published Updated Summary written by a model

8.5HighCNA
Exploited
No known exploitation
Fix
Vendor patch: 63755ff
Who is exposed
Specific setups only

Do first: Check whether your setup matches what the bug needs. Affects WLA DX versions 9.7 through 10.7. The attacker-supplied object or library file has a section namespace longer than 255 bytes or without a terminator, and is linked by wlalink.

Summary

WLA DX from Ville Helin contains a stack-based buffer overflow in the parse_data_blocks() function of its wlalink component. A local attacker, without needing to log in, can supply a crafted object or library file that overflows the buffer when a user links it.

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

Who should check

Anyone running WLA DX 9.7 through 10.7, especially the wlalink linker, including teams that link third-party object or library files.

“Affecting WLA DX >= 9.7, <= 10.7”

vulncheck.com

cve.now Index

15Pcve.now Index 15 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure5/25Specific setups only
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity9.5/10CVSS 8.5, total technical impact per CISA
  • No patch0/5No signal

What would change the score

  • Would score about 65 if added to CISA KEV
  • Would score about 60 if CISA's SSVC rates exploitation active
  • Would score about 25 if CISA's SSVC rates it automatable

What to do

  • Check whether your setup matches what the bug needs.

    Affects WLA DX versions 9.7 through 10.7. The attacker-supplied object or library file has a section namespace longer than 255 bytes or without a terminator, and is linked by wlalink.
  • Apply the vendor's patch: 63755ff.

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-131871 (WLA DX 9.7 through 10.7 Stack Buffer Overflow via wlalink parse_data_blocks()), 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-131871 (entry last updated 2026-11-18):
Affected:
- Ville Helin WLA DX: from 9.7, through 10.7
Vendor patches: 63755ff (source: https://github.com/vhelin/wla-dx/commit/63755ffcd12f78d3bbadf3b24796383c734c4d77). Check each asset for these patch ids, not only its version.
Conditions (all must be true for the bug to be hit):
- Affects WLA DX versions 9.7 through 10.7. (source: https://www.vulncheck.com/advisories/wla-dx-9.7-through-10.7-stack-buffer-overflow-via-wlalink-parse-data-blocks)
- The attacker-supplied object or library file has a section namespace longer than 255 bytes or without a terminator, and is linked by wlalink. (source: https://www.vulncheck.com/advisories/wla-dx-9.7-through-10.7-stack-buffer-overflow-via-wlalink-parse-data-blocks)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: local access, no login, a user action.
CISA KEV: CVE-2026-131871 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-131871 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/vhelin/wla-dx/commit/63755ffcd12f78d3bbadf3b24796383c734c4d77
- https://github.com/vhelin/wla-dx/blob/v10.7/wlalink/analyze.c#L2152-L2156
- https://github.com/vhelin/wla-dx
- https://www.vulncheck.com/advisories/wla-dx-9.7-through-10.7-stack-buffer-overflow-via-wlalink-parse-data-blocks
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-131871
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-131871"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: total

  4. Record last updated

Affected versions

  • Ville Helin WLA DX

    From 9.7 · through 10.7

Evidence 6

Corrections

None so far.

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

Questions about CVE-2026-131871

Is CVE-2026-131871 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

What does this mean?

A stack-based buffer overflow in parse_data_blocks() in wlalink can corrupt memory on the machine running the linker while it links a crafted object or library file. The overflow involves a section namespace longer than 255 bytes or one without a terminator.Source: vulncheck.com, github.com

Which versions are affected by CVE-2026-131871?

WLA DX: from 9.7 through 10.7.Source: cve.now feed data

Am I affected, and how do I check?

WLA DX versions 9.7 through 10.7 are in the affected range. The risky input is an object or library file with a section namespace longer than 255 bytes or unterminated, which wlalink links. Check the installed WLA DX version against that range to see whether it falls within it.Source: vulncheck.com, github.com

How do I fix CVE-2026-131871?

The vendor's fix is patch 63755ff, and the advisory names no fixed version. Apply that patch to the linker.Source: vulncheck.com, github.com

More CVEs