Vulnerability in Iris (CVE-2026-41522)
Summary
Vulnerability in Iris (CVE-2026-41522). Risk of unauthorized operations or information disclosure. Exploitable via case.iocs. Mitigation: upgrade to 2.4.28 or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-41522 has been found in Iris.
Attackers can target a specific entry point like case.iocs over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade Iris to 2.4.28 or later.
If unsure, ask your IT team or search "Iris CVE-2026-41522" on the vendor's site.
CVE-2026-41522 (Iris) — CWE-285
Attack surface: case.iocs / graphene / graphql_blueprint / register_blueprint
Patched: 2.4.28 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-285) exists in Iris. Attackers reach the vulnerable code path via case.iocs.
Check the vendor advisory for the affected versions of Iris. Attack surface: case.iocs / graphene / graphql_blueprint / register_blueprint.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 2.4.28.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'Iris' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'Iris' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Irisを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade Iris to 2.4.28ステージング環境で 2.4.28 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。