dbcve.org
Improper AuthorizationWeakness · CWE-285

CVE-2026-41522

HIGH · 7.1 CVSS v4.0 Published 2026-06-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
Remotely reachable Zero-click

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 · unedited
Iris is a web collaborative platform that helps incident responders share technical details during investigations. Prior to version 2.4.28, DFIR-IRIS exposes an optional GraphQL endpoint at `/graphql` that does not enforce the same authorization checks as the REST API. Any authenticated user can abuse it in three ways: unauthorized IOC read across cases (IDOR), bulk IOC disclosure via `case.iocs`. The `case(caseId: …).iocs` resolver returns IOCs linked to an arbitrary case without verifying the caller has access to that case, and unauthorized case creation. All three are reachable by any authenticated user, regardless of role or case ACL. This is fixed in v2.4.28. The GraphQL blueprint, resolvers, and dependencies (`graphene`, `graphene-sqlalchemy`, `graphql-server[flask]`) were removed entirely, since the feature was not in use. As a workaround, block `/graphql` at the reverse proxy (recommended) or comment out the `graphql_blueprint` import and `register_blueprint` call in `source/app/views.py` and restart.

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 confidence

The Iris incident response platform exposes a GraphQL endpoint at /graphql that bypasses authorization checks present in the REST API. Any authenticated user can read IOCs from cases they don't have access to (IDOR), perform bulk IOC disclosure via the case.iocs resolver, and create cases without proper ACL verification. The vulnerability exists because GraphQL resolvers don't validate user access to the requested case before returning data.

MitigationUpgrade to v2.4.28 which removes the GraphQL feature entirely, or block /graphql at the reverse proxy as a workaround.

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
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify if the /graphql endpoint is accessible
    Send an HTTP request to your Iris instance at /graphql (e.g., curl -k https://your-iris-host/graphql)
    Affected if The endpoint responds with GraphQL schema or accepts queries (returns 200 instead of 404/403)
  2. Check the installed Iris version
    Inspect the Iris installation directory or check the version via the application's REST API or package manager used during installation
    Affected if The version is below v2.4.28 (e.g., v2.4.0 through v2.4.27)
  3. Confirm GraphQL is enabled in the configuration
    Look for GraphQL-related settings in the Iris configuration files (commonly in config/, settings/, or the main application configuration)
    Affected if GraphQL or /graphql is explicitly enabled, or no disabled flag exists for it
  4. Test unauthorized IOC access via GraphQL
    Log in as a standard user with limited case access, then send a GraphQL query to /graphql requesting IOCs from a case ID outside your assigned cases
    Affected if The query returns IOC data from cases you should not have access to (confirms the IDOR vulnerability)

You are affected if your Iris version is below v2.4.28 and the /graphql endpoint is exposed and accessible, allowing unauthorized access to case IOCs or unauthorized case creation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to v2.4.28 which removes the GraphQL feature entirely, or block /graphql at the reverse proxy as a workaround.

Recommended fix High confidence

Upgrade to Iris v2.4.28 or later

  1. 1. Back up your current Iris installation and database before proceeding
  2. 2. Check your current Iris version (likely via --version flag or administrative UI)
  3. 3. Upgrade to version 2.4.28 or later
  4. 4. Verify the upgrade was successful and the /graphql endpoint is no longer accessible
  5. 5. Test that normal IRIS functionality (REST API, case management, IOC handling) continues to work correctly
Caveat The GraphQL endpoint and all associated functionality (graphene, graphene-sqlalchemy, graphql-server[flask]) were entirely removed; any custom integrations relying on /graphql will no longer work

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-41522 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-41522 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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