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.
CVE-2026-107336
Score 6.5 from GitHub Security Advisory published 2026-10-08. A secondary CVSS source baseline 6.5; sources differ by 0.0.
- Lower severity and no public exploit yet
No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.
- CVSS v3
- 6.5
- EG Score
- 6.5MEDIUMhigh confidence
- EG Risk
- 44EG Risk 44/100CISA SSVC
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity65% × 45%Exploitation0% × 40%Automatability100% × 15%CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix. - EPSS PROB
- 0.2%
- EPSS %ILE
- 14th
- KEV
- Not listed
CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).
No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table
Published
October 8, 2026
Last Modified
October 8, 2026
Advisory Details (2)
Auto-updated Oct 8, 2026CSAF/csaf_files/OT/white/2026/icsa-26-280-01.json at develop · cisagov/CSAF · GitHub
https://github.com/cisagov/CSAF/blob/develop/csaf_files/OT/white/2026/icsa-26-280-01.jsonUnauthenticated bypass of the nginx auth gate on the /iddash2ark/ Arkime shortcut (regex case-sensitivity mismatch + forwarded-identity confused deputy) · Advisory · cisagov/Malcolm · GitHub
https://github.com/cisagov/Malcolm/security/advisories/GHSA-7j32-cf27-cp6hVendor Advisories for CVE-2026-107336(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(3)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 11× in last 7d / 11× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-10-09 20:06 UTCEPSS rescore
- 2026-10-09 18:55 UTCGHSA enrichment
- 2026-10-08 21:16 UTCGHSA enrichment
- 2026-10-08 20:20 UTCEG score recompute
- 2026-10-08 20:20 UTCGHSA enrichment
- 2026-10-08 19:25 UTCEG score recompute
- 2026-10-08 19:25 UTCGHSA enrichment
- 2026-10-08 18:36 UTCEG score recompute
- 2026-10-08 18:36 UTCGHSA enrichment
- 2026-10-08 17:30 UTCEG score recompute
- 2026-10-08 17:29 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-863 · CWE-290 · CWE-441
Frequently asked(5)
What is CVE-2026-107336?
When was CVE-2026-107336 disclosed?
Is CVE-2026-107336 actively exploited?
What is the CVSS score of CVE-2026-107336?
How do I remediate CVE-2026-107336?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-107336
Is Your Infrastructure Affected by CVE-2026-107336?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.