# CVE-2026-111946: Plack::Middleware::ETag versions from 0.04 before 0.06 for Perl disclose file inode numbers in the default ETag header

> An attacker can obtain file inode numbers from ETag headers, aiding backend fingerprinting and file correlation.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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:** 19 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-943g-rgq5-6xc8

## What is CVE-2026-111946?

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

### Official description

Plack::Middleware::ETag versions from 0.04 before 0.06 for Perl disclose file inode numbers in the default ETag header.

When the response body is a filehandle and the file_etag option is not set, the ETag is built from the file's inode number, modification time and size. Clients receiving affected responses may use the disclosed inode numbers to aid backend fingerprinting and correlation of files served through different URLs.

Weakness: CWE-497 (Exposure of Sensitive System Information to an Unauthorized Control Sphere)

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


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

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

## Is CVE-2026-111946 being exploited?

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

## Fix prompt for AI coding agents

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

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

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

## Sources

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

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