Skip to main content
VulnerabilityPublished

CVE-2026-1435: Graylog Web Interface · Insufficient Session Expiration

Affects Graylog Web InterfaceSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.3 Critical.

Data as of 15 Nov 2026, 20:25 UTC

CVSS 4.0 base score
9.3Critical
How severe the flaw is on the 0–10 CVSS scale.

Contested

Critical score, yet low EPSS after six months
EPSS
0.4% chance of exploitation in 30 days – higher than 37% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Feb 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
GraylogGraylog Web InterfaceAffected
  • =2.2.3
Fixed in–

AI-suggested

Immediate mitigation steps include restricting network access to the Graylog web interface and API endpoints by implementing strict firewall rules and network segmentation to limit exposure to trusted users only. Organizations should enforce multi-factor authentication (MFA) on Graylog accounts to reduce the risk of session token theft leading to unauthorized access. Monitoring for unusual session activity and implementing session timeout policies can help detect and limit the impact of reused session tokens. Administrators should review and revoke any suspicious or inactive sessions manually if the Graylog interface allows it. Until an official patch is released, consider deploying Web Application Firewalls (WAFs) with custom rules to detect and block reuse of old session tokens. Regularly update Graylog to the latest versions once patches addressing this vulnerability become available. Additionally, educate users on secure session management practices and the risks of session token leakage. Conduct thorough audits of Graylog access logs to identify potential exploitation attempts. Finally, coordinate with Graylog vendor support for updates and guidance on secure configuration.

Description

Not properly invalidated session vulnerability in Graylog Web Interface, version 2.2.3, due to incorrect management of session invalidation after new logins. The application generates a new 'sessionId' each time a user authenticates, but does not invalidate previously issued session identifiers, which remain valid even after multiple consecutive logins by the same user. As a result, a stolen or leaked 'sessionId' can continue to be used to authenticate valid requests. Exploiting this vulnerability would allow an attacker with access to the web service/API network (port 9000 or HTTP/S endpoint of the server) to reuse an old session token to gain unauthorized access to the application, interact with the API/web, and compromise the integrity of the affected account.

References

Community reviews

Loading reviews…