CVE-2026-107336: CWE-290 Authentication bypass by spoofing in CISA Malcolm
Description
Malcolm's front nginx reverse proxy defines a "Dashboards → Arkime shortcut" location using a case-insensitive regex matcher but a case-sensitive rewrite. A request whose path segment is not exact-lowercase (for example /IDDASH2ARK/...) enters the location (the matcher fires) but evades the rewrite (no redirect is issued), so nginx falls through to the location's proxy_pass to the Arkime backend. That location is the one proxied location in the shipped config that does not include the per-location authentication file, so the request reaches Arkime unauthenticated. The same location also forwards a client-supplied X-Forwarded-User header un-overwritten, and Arkime is configured to trust X-Forwarded-User as the authenticated username — so an unauthenticated network caller can reach the Arkime backend while supplying a forged, auto-provisioned identity.
CVSS v3.1
Score 6.5medium
Affected software
CISA
Malcolm
pkg:github/cisagov/MalcolmRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Malcolm's front nginx reverse proxy defines a 'Dashboards → Arkime shortcut' location using a case-insensitive regex matcher but a case-sensitive rewrite. Requests with path segments not in exact lowercase (e.g., /IDDASH2ARK/...) match the location but evade the rewrite, causing nginx to proxy the request to the Arkime backend without authentication. The proxied location lacks per-location authentication, and the proxy forwards the client-supplied X-Forwarded-User header unaltered. Since Arkime trusts this header as the authenticated username, an unauthenticated network caller can supply a forged identity and gain unauthorized access to Arkime.
Potential Impact
An attacker can bypass authentication controls and access the Arkime backend with a forged identity by exploiting the mismatch between case-insensitive matching and case-sensitive rewriting in the nginx proxy configuration. This results in unauthorized access with limited confidentiality and integrity impact as per the CVSS score, but no availability impact.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, users should review and correct the nginx reverse proxy configuration to ensure consistent case handling between matching and rewriting, and ensure that authentication is enforced on all proxied locations. Additionally, Arkime should not trust client-supplied X-Forwarded-User headers without proper validation.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- icscert
- Date Reserved
- 2026-10-07T18:31:15.966Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6ac7d49a2cdf04f6562c68ad
Added to database: 10/08/2026, 17:36:26 UTC
Last enriched: 10/08/2026, 17:48:52 UTC
Last updated: 10/08/2026, 21:45:58 UTC
Views: 8
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.