# CVE-2026-41522: Iris has an Improper Authorization issue

> Authenticated users can bypass case access controls via an optional GraphQL endpoint to read or create incident data.

- **Severity:** High 7.1 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Jun 2026
- **Updated:** 8 Jun 2026
- **Also known as:** GHSA-3mxh-x92q-9r25

## What is CVE-2026-41522?

CVE-2026-41522 is a high-severity missing authorization vulnerability in dfir-iris iris-web, published on 4 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-285 (Improper Authorization)

## Which versions are affected by CVE-2026-41522?


## How do I fix CVE-2026-41522?

No fix has been published for CVE-2026-41522 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-41522 being exploited?

There is no known exploitation of CVE-2026-41522 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-41522 and fix it if it is affected.

What it is: CVE-2026-41522 is a high-severity missing authorization vulnerability in dfir-iris iris-web, published on 4 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-41522 in the wild and no public exploit code.

Affected product: dfir-iris iris-web. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-41522/ (Markdown: https://insights.sbomify.com/CVE-2026-41522/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-41522
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-41522
- OSV: https://osv.dev/vulnerability/CVE-2026-41522

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-41522/
Summaries are generated and may contain mistakes; the official description above is the record.