{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-111946 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-111946 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-111946 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2026-111946 in the wild and no public exploit code.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-111946/ (Markdown: https://insights.sbomify.com/CVE-2026-111946/index.md)","id":"CVE-2026-111946","markdown":"https://insights.sbomify.com/CVE-2026-111946/index.md","name":"CVE-2026-111946","record":{"aliases":["GHSA-943g-rgq5-6xc8"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Perl Plack middleware","requires_auth":"none","summary":"An attacker can obtain file inode numbers from ETag headers, aiding backend fingerprinting and file correlation.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CPANSec","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-497","name":"Exposure of Sensitive System Information to an Unauthorized Control Sphere"}],"description":"Plack::Middleware::ETag versions from 0.04 before 0.06 for Perl disclose file inode numbers in the default ETag header.\n\nWhen 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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Plack::Middleware::ETag versions from 0.04 before 0.06 for Perl disclose file inode numbers in the default ETag header","id":"CVE-2026-111946","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"Easy Pricing Tables \u003c 4.1.3 - Contributor+ Arbitrary Post Clone and Publish via Legacy Table Duplication","id":"CVE-2026-111947"},"packages":[],"prev":{"headline":"Distrust compromised intermediate certificates in crypto/x509","id":"CVE-2026-111943"},"products":[],"published":"2026-10-19","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-29","vendors":[]},"summary":"An attacker can obtain file inode numbers from ETag headers, aiding backend fingerprinting and file correlation.","url":"https://insights.sbomify.com/CVE-2026-111946/"}