Skip to main content
Mallory
UnratedVulnerability

CVE-2026-110336: Path-Based Access-Control Bypass in Plack FCGI and Apache2 Handlers

Updated 17 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days3 mentions · peak 2 in a dayToday
CVSS-Not scored
EPSS-30-day exploit probability
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-110336CWE-180

CVE-2026-110336 concerns path-handling behavior in Plack::Handler::FCGI and Plack::Handler::Apache2, which preserve dot segments in PATH_INFO. Deployments that rely on front-server path-based access controls can be exposed to authorization bypass when the front server and application interpret or normalize these paths differently. The associated Plack change documents this behavior and warns against relying on front-server path-based access control. Affected and fixed version boundaries are not specified.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can bypass path-based access restrictions and expose protected application resources or functionality. The consequences depend on the resources reachable through the affected deployment. Advisory severity metrics disagree on integrity and availability impacts; specific mechanisms for data modification, denial of service, or code execution are not established.

Mitigation

If you can’t patch tonight, do this now.

Do not rely exclusively on front-server path-based access controls. Enforce authorization within the application against the same canonical path representation used for routing and resource access. Reject ambiguous dot-segment paths before dispatch where feasible, and verify that front-server and application path interpretation cannot expose protected routes.

Remediation

Patch, then assume compromise.

Apply the applicable distribution security updates for Plack packages where available. Fedora and FreeBSD advisories recommend package updates, but the change specifically associated with this CVE documents existing handler behavior rather than establishing a normalization fix. A Debian-related advisory lists no vendor patch or known solution. Review application authorization and path handling independently of package updates; fixed version boundaries are not available.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2026-110336 exploited in the wild?
As of Nov 4, 2026, Mallory has no reports of CVE-2026-110336 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-110336?
As of Nov 4, 2026, Mallory has found no public exploit for CVE-2026-110336.
Is there a patch for CVE-2026-110336?
Apply the applicable distribution security updates for Plack packages where available. Fedora and FreeBSD advisories recommend package updates, but the change specifically associated with this CVE documents existing handler behavior rather than establishing a normalization fix.
Activity feed

Recent activity

6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
tenable nessus pluginsNews · Nov 4, 2026Fedora 44 : perl-Plack / perl-Plack-Middleware-ReverseProxy (2... | Tenable®A path-handling security issue involving retained dot segments in PATH_INFO with Plack's FCGI and Apache2 handlers. The advisory warns against relying on front-server path-based access controls. Updated packages are available, but the listed change for this CVE is documentation rather than an explicit behavioral fix.Read more ↗tenable nessus pluginsNews · Nov 4, 2026Fedora 43 : perl-Plack / perl-Plack-Middleware-ReverseProxy (2... | Tenable®The scoring reference for Fedora advisory 2026-1f56c920d8. The supplied CVSS v3 vector indicates network exploitation with low complexity, no privileges or user interaction required, and high confidentiality and availability impacts without integrity impact. The content does not explain the underlying flaw or identify its specific affected package. The advisory lists a patch publication date of October 18, 2026, and states that no known exploits are available.Read more ↗tenable nessus pluginsNews · Oct 31, 2026Fedora 45 : perl-Plack / perl-Plack-Middleware-ReverseProxy (2... | Tenable®A path-handling security issue involving preservation of dot segments in PATH_INFO by Plack's FCGI and Apache2 handlers. The advisory warns against relying on front-server path-based access control and identifies a documentation update addressing this behavior.Read more ↗tenable nessus pluginsNews · Oct 19, 2026Linux Distros Unpatched Vulnerability : CVE-2026-110336 | Tenable®A critical vulnerability affecting Plack, identified through the Debian libplack-perl package. The reference assigns a CVSS v3 base score of 9.8, indicating network accessibility without authentication or user interaction and high confidentiality, integrity, and availability impacts. It does not describe the underlying flaw. Nessus detects exposure based on vendor-reported package presence rather than exploitation testing. The vendor indicates the vulnerability will not be patched, and no known solution is provided.Read more ↗
+2 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.