# CVE-2026-111450: Information disclosure in Wheels

> Attackers can redirect error emails to their address by manipulating the Host header, potentially exposing sensitive configuration and session data.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-109532, GHSA-8gcv-3v9h-7gj2, GHSA-fg56-4rxr-cx5x

## What is CVE-2026-111450?

CVE-2026-111450 is a medium-severity vulnerability in Wheels, published on 16 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Wheels through 4.1.1 derives its default production error-email address from the Host header of the request that starts the application. If no explicit error-email recipient is configured, a mail server is configured, and the server accepts an attacker-chosen Host, an attacker whose request triggers a cold start can direct later error emails to an address under their control for that application's lifetime. Emails disclose error and request metadata; on engines/versions where scope dumps render, they may also disclose configuration secrets and other users' session/cookie data. On the Lucee 7 engine, scope dumps fail to render, limiting disclosure to header fields. This is fixed in 4.1.2.

Weakness: CWE-348 (Use of Less Trusted Source)

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


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

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

## Is CVE-2026-111450 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-111450 is a medium-severity vulnerability in Wheels, published on 16 Oct 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-111450 in the wild and no public exploit code.

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

## Sources

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

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