Skip to main content
Mallory
UnratedVulnerability

CVE-2026-96631: Cookie Attribute Injection in AdminNeo via X-Forwarded-Prefix

Updated 22 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-96631CWE-20

AdminNeo versions 4.6.0 through versions before 5.5.1 contain a cookie attribute injection vulnerability. AdminNeo prepends the unvalidated X-Forwarded-Prefix request header to REQUEST_URI, which is subsequently used to derive cookie paths. Its cookie() function manually constructs Set-Cookie headers without neutralizing semicolon delimiters in the derived path, allowing attacker-controlled prefix values to introduce additional cookie attributes. The tainted URI also influences PHP session cookie parameters through session_set_cookie_params(). Successful exploitation can alter cookie scope or security behavior, with potential consequences including session compromise and credential exposure.

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.

Injected attributes can affect cookie Domain, Path, Secure, and SameSite behavior. Potentially affected cookies include the PHP session identifier, the encryption key used for database passwords stored in the session, and user preferences. The resulting risks include session hijacking, session fixation, and database credential exposure. These outcomes are conditional: demonstrated response-header manipulation does not establish successful browser acceptance or cookie exfiltration. Browsers reject Domain attributes targeting unrelated domains, and appended request-path text can invalidate injected attribute values. Actual impact depends on browser parsing, deployment domain relationships, proxy configuration, and access to session-stored encrypted credentials.

Mitigation

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

Configure reverse proxies to discard client-supplied X-Forwarded-Prefix values and provide only a trusted, deployment-defined static prefix. Ensure upstream proxy or middleware configuration cannot pass attacker-controlled prefix values to AdminNeo. In Traefik deployments, use trusted stripPrefix middleware rather than accepting client-controlled prefix headers.

Remediation

Patch, then assume compromise.

Upgrade adminneo-org/adminneo to version 5.5.1 or later. Code-level remediation includes validating X-Forwarded-Prefix before incorporating it into REQUEST_URI, rejecting cookie delimiters and HTTP header metacharacters, and validating the resulting cookie paths. Replace manual Set-Cookie header construction with PHP's setcookie() or setrawcookie() APIs while retaining appropriate input validation.

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-96631 exploited in the wild?
As of Oct 31, 2026, Mallory has no reports of CVE-2026-96631 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-96631?
As of Oct 31, 2026, Mallory has found no public exploit for CVE-2026-96631.
Is there a patch for CVE-2026-96631?
Upgrade adminneo-org/adminneo to version 5.5.1 or later. Code-level remediation includes validating X-Forwarded-Prefix before incorporating it into REQUEST_URI, rejecting cookie delimiters and HTTP header metacharacters, and validating the resulting cookie paths.
Activity feed

Recent activity

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

View more in app →
tenable cloud security pluginsNews · Oct 31, 2026SCA: security update for adminneo-org/adminneo (GHSA-79wv-8rh2... | Tenable®A vulnerability affecting adminneo-org/adminneo packages, identified by Tenable Cloud Security plugin 478075. The listing references CWE-113 and CWE-20 but does not describe the attack mechanism, impact, affected versions, or fixed versions. The plugin's informational severity is not a stated severity rating for the vulnerability.Read more ↗cvefeed high severityNews · Oct 30, 2026CVE-2026-96631 - AdminNeo Cookie Attribute Injection VulnerabilityA cookie attribute injection vulnerability in AdminNeo, rated High with CVSS 3.1 score 8.2. An attacker able to influence X-Forwarded-Prefix can inject cookie attributes because the header is incorporated into REQUEST_URI and subsequently used without adequate sanitization in cookie paths. The advisory describes potential session hijacking, database credential exposure, and cookie scope manipulation. Public proof-of-concept requests are included. Mitigations include sanitizing the header, using secure cookie-setting functions, validating cookie paths, and configuring proxies to supply a static trusted prefix. References include a fix commit and the v5.5.1 release.Read more ↗ghsa syntheticNews · Oct 30, 2026GHSA-79wv-8rh2-9vp2AdminNeo incorporates an unvalidated X-Forwarded-Prefix header into REQUEST_URI and subsequently into cookie paths, permitting cookie attribute injection when an attacker can influence that header. The advisory describes potential session hijacking, credential theft, and cookie-scope manipulation affecting neo_sid, neo_key, and neo_settings. Public curl proof-of-concept requests demonstrate header injection. The claimed exfiltration to arbitrary unrelated domains is not established by these examples and remains constrained by browser cookie-domain validation.Read more ↗
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.