Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2026-18361: Stored XSS in DFIR-IRIS datastore upload

Published Jul 30, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.6High · v3.1
EPSS0.21%11th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
IdentifiersCVE-2026-18361CWE-79 · Improper Neutralization of Input…

CVE-2026-18361 is a stored cross-site scripting vulnerability in the DFIR-IRIS web application, confirmed in version 2.4.26 and possibly affecting additional versions. The flaw is present in the datastore upload functionality, where an authenticated attacker can upload an SVG file containing active script content. When the uploaded content is later viewed through the application, the browser executes attacker-controlled JavaScript because the application serves the file as SVG content and renders it inline rather than forcing download. The issue stems from unsafe handling of user-controlled uploaded content in a browser-executable format, enabling persistent script execution in the context of the application.

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 allows attacker-supplied JavaScript to run in the browser of another user who views the malicious datastore content. This can enable session hijacking, account compromise, unauthorized actions performed in the victim's context, and exposure of sensitive application data. If an administrative user is targeted, the vulnerability can facilitate full takeover of the DFIR-IRIS application.

Mitigation

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

Until a patch is available, restrict datastore uploads to non-active file types where possible, or block SVG uploads entirely. If SVG support is required, sanitize uploaded SVG content to remove script-capable elements and attributes, and serve such files with download-oriented handling rather than inline rendering. As defense in depth, harden the Content Security Policy, including removal of unsafe-inline, to reduce the likelihood and impact of script execution.

Remediation

Patch, then assume compromise.

Upgrade to a vendor-fixed release once one is available. The datastore upload and file-serving workflow should be changed so that uploaded active content, especially SVG, cannot execute script in the application context. Recommended corrective measures include sanitizing or rejecting unsafe uploaded content, serving uploaded SVG and similar files as attachments instead of inline-rendered content, and applying consistent output-handling controls for user-supplied data throughout the application.

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-18361 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-18361 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-18361?
Yes. As of Sep 25, 2026, Mallory has reports of a public exploit for CVE-2026-18361.
Is there a patch for CVE-2026-18361?
Upgrade to a vendor-fixed release once one is available. The datastore upload and file-serving workflow should be changed so that uploaded active content, especially SVG, cannot execute script in the application context.
How severe is CVE-2026-18361?
CVE-2026-18361 has a CVSS v3.1 score of 7.6 (High) and an EPSS score of 0.21% (11th percentile) as of Sep 25, 2026.
Activity feed

Recent activity

2 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.

View more in app →

No news coverage yet. Advisories and community discussion only.

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 activity2Community discussion across Reddit, Mastodon, and other social sources.