Skip to main content
Mallory
MediumPublic exploitVulnerability

CVE-2026-16970: Ineffective Logout in DFIR-IRIS IRIS

Published Jul 30, 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.
CVSS4.2Medium · v3.1
EPSS0.22%12th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
IdentifiersCVE-2026-16970CWE-613 · Insufficient Session Expiration

CVE-2026-16970 is an insufficient session expiration vulnerability in the DFIR-IRIS IRIS web application, confirmed in version 2.4.26 and possibly affecting other versions. The logout mechanism removes the session cookie from the client side but does not invalidate the corresponding authenticated session on the server side. As a result, a previously captured valid session cookie remains usable after the user logs out, and authenticated requests made with that old cookie continue to succeed. This is a classic ineffective logout condition that undermines expected session termination semantics and enables session hijacking to persist beyond logout.

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.

An attacker who has obtained a valid session cookie can continue to access authenticated application resources even after the legitimate user logs out. The flaw therefore enables persistent unauthorized access within the scope of the hijacked session, with potential exposure of sensitive data and continued use of the victim's authenticated privileges until the server-side session eventually expires or is otherwise invalidated.

Mitigation

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

Until a vendor fix is available, reduce session lifetime and idle timeout values where possible, force re-authentication for sensitive actions, and administratively invalidate active sessions after suspected compromise or user logout events. Monitor for reuse of old session identifiers after logout and consider compensating controls such as reverse-proxy or application-layer session management that can enforce server-side revocation semantics. Users and administrators should treat logout as unreliable for terminating compromised sessions until the issue is corrected.

Remediation

Patch, then assume compromise.

Implement server-side session invalidation during logout so that the associated session identifier is immediately revoked and cannot be reused. Logout should destroy server-side session state, release related session resources, and require full re-authentication before further access. Once a vendor fix is available, upgrade to the corrected version. After remediation, invalidate existing active sessions and rotate session cookies to ensure previously captured tokens cannot be reused.

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-16970 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-16970 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-16970?
Yes. As of Sep 25, 2026, Mallory has reports of a public exploit for CVE-2026-16970.
Is there a patch for CVE-2026-16970?
Implement server-side session invalidation during logout so that the associated session identifier is immediately revoked and cannot be reused. Logout should destroy server-side session state, release related session resources, and require full re-authentication before further access.
How severe is CVE-2026-16970?
CVE-2026-16970 has a CVSS v3.1 score of 4.2 (Medium) and an EPSS score of 0.22% (12th percentile) as of Sep 25, 2026.
Activity feed

Recent activity

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