Skip to main content
Mallory
MediumPublic exploitVulnerability

CVE-2026-42547: Incorrect authorization in DFIR-IRIS alert customer assignment

Published Jun 4, 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.
CVSS5.4Medium · v3.1
EPSS0.17%7th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
IdentifiersCVE-2026-42547CWE-863 · Incorrect Authorization

CVE-2026-42547 is an authorization flaw in DFIR-IRIS IRIS affecting versions up to and including 2.4.27. The issue arises because alert updates do not properly enforce authorization checks on security-relevant properties, specifically allowing a user with alerts_write privileges to create an alert for a customer they are authorized to access and then modify the alert_customer_id field to a different customer to whom they are not assigned. The vulnerable update path accepts the unauthorized customer reassignment as long as database constraints are satisfied. This enables false attribution of alerts to other customers and breaks tenant/customer access boundaries. The issue was fixed in IRIS version 2.4.28.

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 an authenticated low-privilege user with alert-writing capability to assign or reassign alerts to unauthorized customers, resulting in integrity impact through false alert attribution and limited confidentiality impact across customer boundaries. An attacker can plant fake alerts under another customer, potentially misleading responders or contaminating investigative workflows. The advisory also notes that, when combined with cross-site scripting, the flaw can be leveraged to exfiltrate alerts belonging to other customers by inducing privileged users to perform unauthorized reassignment actions. No direct availability impact is described.

Mitigation

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

If immediate upgrade is not possible, restrict or harden the alert update API so that users cannot modify customer-assignment fields except through explicitly authorized workflows. Apply strict server-side validation of updated alert properties against the same authorization rules used during alert creation and UI operations. Limit alerts_write privileges to only trusted users, monitor for anomalous alert reassignments between customers, and reduce exposure to cross-site scripting because the advisory states XSS can amplify the issue into cross-customer alert exfiltration.

Remediation

Patch, then assume compromise.

Upgrade DFIR-IRIS to version 2.4.28 or later, which contains the vendor patch for CVE-2026-42547. In addition, ensure the alert update API only permits modification of fields that are intended to be editable and enforce server-side authorization checks on all security-relevant properties, including customer assignment fields such as alert_customer_id. Reject update requests that would violate customer-assignment access rules.

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-42547 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-42547 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-42547?
Yes. As of Sep 25, 2026, Mallory has reports of a public exploit for CVE-2026-42547.
Is there a patch for CVE-2026-42547?
Upgrade DFIR-IRIS to version 2.4.28 or later, which contains the vendor patch for CVE-2026-42547. In addition, ensure the alert update API only permits modification of fields that are intended to be editable and enforce server-side authorization checks on all security-relevant properties, including customer assignment fields such as alert_customer_id.
How severe is CVE-2026-42547?
CVE-2026-42547 has a CVSS v3.1 score of 5.4 (Medium) and an EPSS score of 0.17% (7th percentile) as of Sep 25, 2026.
Activity feed

Recent activity

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