# CVE-2026-75031: Code injection in Interchange

> Unauthenticated attackers can inject and execute arbitrary Perl code via the quick question admin feature, leading to remote code execution.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Sep 2026
- **Updated:** 18 Sep 2026
- **Also known as:** GHSA-84xw-5r3f-vrrr

## What is CVE-2026-75031?

CVE-2026-75031 is a critical code injection vulnerability in Interchange, published on 18 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In the interchange/interchange project, a critical remote code execution (RCE) vulnerability was found in the 
“quick question” admin feature. In default installations arbitrary Perl 
code can be injected and executed server-side by unauthenticated users. 
The Perl code normally runs within a Safe container which limits the 
scope of what it can do, unless the non-default AllowGlobal directive is
 configured for the catalog being accessed.CTOR]

Weakness: CWE-94 (Improper Control of Generation of Code)

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


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

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

## Is CVE-2026-75031 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-75031 is a critical code injection vulnerability in Interchange, published on 18 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-75031 in the wild and no public exploit code.

Affected product: Interchange. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-75031/ (Markdown: https://insights.sbomify.com/CVE-2026-75031/index.md)
```

## Sources

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

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