Graylog Web Interface 2.2.3 session expiration

Summaryinfo

A vulnerability was found in Graylog Web Interface 2.2.3. It has been classified as critical. Affected is an unknown function of the component Web Interface. This manipulation causes session expiration. This vulnerability is tracked as CVE-2026-1435. The attack is possible to be carried out remotely. No exploit exists.

Detailsinfo

A vulnerability has been found in Graylog Web Interface 2.2.3 and classified as critical. Affected by this vulnerability is an unknown code block of the component Web Interface. The manipulation with an unknown input leads to a session expiration vulnerability. The CWE definition for the vulnerability is CWE-613. According to WASC, "Insufficient Session Expiration is when a web site permits an attacker to reuse old session credentials or session IDs for authorization." As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

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.

The weakness was disclosed by Julen Garrido Estévez. The advisory is shared at incibe.es. This vulnerability is known as CVE-2026-1435 since 01/26/2026. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 02/20/2026).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the vulnerability database at CERT Bund (WID-SEC-2026-0458). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Affected

• Open Source Graylog

Productinfo

Vendor

• Graylog

Name

• Web Interface

Version

• 2.2.3

CPE 2.3info

• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion