Skip to main content
Menu
CVEs

CVE

Chris Spiegel Gargoyle stack buffer overflow in Plus interpreter via ReadAction()

CVE-2026-131873EUVD-2026-128393GHSA-VMQR-JVMR-4XCVPublished Updated Summary written by a model

6.9MediumCNA
Exploited
No known exploitation
Fix
Fix or patch referenced
Who is exposed
Not reported

Do first: Apply the patch listed under Evidence.

Summary

Gargoyle from Chris Spiegel has a stack-based buffer overflow in its bundled Plus interpreter. A local attacker who gets a user to open a crafted or truncated .plus game file can trigger it without logging in, and the overflow can write file-controlled values past an array and crash the player.

Original description

Gargoyle 2023.1 through 2026.1.1 contains a stack-based buffer overflow vulnerability in the bundled Plus interpreter's ReadAction() function in terps/plus/loaddatabase.c, which never bounds-checks the index into the 1024-entry conditions array. Attackers can supply a crafted or truncated .plus game file with unterminated action conditions to write file-controlled values past the array and crash the player.

cve.now Index

7Pcve.now Index 7 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure?/25Unknown. No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity6.9/10CVSS 6.9
  • No patch0/5No signal

What would change the score

  • Would score about 62 if added to CISA KEV
  • Would score about 57 if CISA's SSVC rates exploitation active
  • Would score about 29 if advisories confirm default setups are exposed

What to do

  • Apply the patch listed under Evidence.

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-131873 (Gargoyle 2023.1 through 2026.1.1 Plus Interpreter Stack Buffer Overflow via ReadAction()), 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-131873 (entry last updated 2026-11-18):
Affected:
- Chris Spiegel Gargoyle: from 2023.1, through 2026.1.1
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-131873 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-131873 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/garglk/garglk/commit/45385f105b825521bf4296ef8d046fbbdd8dda7f
- https://github.com/garglk/garglk/pull/1041
- https://github.com/garglk/garglk/blob/2026.1.1/terps/plus/loaddatabase.c#L732-L742
- https://www.vulncheck.com/advisories/gargoyle-2023.1-through-2026.1.1-plus-interpreter-stack-buffer-overflow-via-readaction
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-131873
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-131873"}.

Timeline

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

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

  4. Record last updated

Affected versions

  • Chris Spiegel Gargoyle

    From 2023.1 · through 2026.1.1

Evidence 7

Corrections

None so far.

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

Questions about CVE-2026-131873

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

Which versions are affected by CVE-2026-131873?

Gargoyle: from 2023.1 through 2026.1.1.Source: cve.now feed data

More CVEs