CVE-2026-42547
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIRIS is a web collaborative platform that helps incident responders share technical details during investigations. In versions prior to 2.4.28, users can create alerts for customers that are not assigned to them. This can be abused to falsely attribute fake alerts to customers. In combination with Cross-Site Scripting, this can also be used to exfiltrate alerts from other customers. Version 2.4.28 contains a patch.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceIRIS versions prior to 2.4.28 contain a broken access control vulnerability where users can create alerts for customers not assigned to them. This allows false attribution of fake alerts and, when combined with cross-site scripting, enables exfiltration of alerts from other customers.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify IRIS installation and versionLocate the IRIS application and determine its installed version number. This is typically found in the application metadata, about page, or version file shipped with the product.Affected if The installed version is prior to 2.4.28 (e.g., 2.4.27, 2.4.0, 1.x, etc.)
-
Verify alert creation functionality is accessibleConfirm that the alert creation feature is enabled and accessible to standard users in the IRIS deployment. Check if users have the ability to create or submit alerts through the UI or API.Affected if Standard users can access and use the alert creation feature
-
Test authorization on alert customer attributionCreate a test alert as a user who is assigned to a specific customer, then attempt to attribute that alert to a different customer to which the user is not assigned. Observe whether the system accepts or rejects this cross-customer attribution.Affected if The system allows alerts to be attributed to customers outside the user's assigned customer scope
-
Review audit logs for unauthorized alert attributionExamine IRIS audit or event logs for any alert creation events where the attributed customer does not match the creating user's customer assignment.Affected if Historical alerts exist with customer attribution that differs from the creating user's assigned customers
A deployment is affected if IRIS version is earlier than 2.4.28 AND users can create alerts for customers they are not assigned to, allowing unauthorized cross-customer alert attribution.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade to IRIS version 2.4.28 or later. Additionally, audit existing alerts for suspicious or unauthorized attributions and remediate any XSS vulnerabilities to prevent the exfiltration attack chain.
IRIS version 2.4.28
- 1. Backup your IRIS installation and database before upgrading
- 2. Upgrade IRIS to version 2.4.28 (or latest stable release)
- 3. Verify the upgrade was successful by checking the IRIS version number
- 4. Test that users can no longer create alerts for customers not assigned to them
- 5. Confirm the authorization controls are working correctly for alert creation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-42547 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-42547 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data