Unauthorized account access via persistent session identifiers
Published Feb 18, 2026 · Updated Feb 18, 2026
Insufficient session expiration in Graylog Web Interface 2.2.3 allows remote attackers to access accounts with an old session identifier. Each successful login creates a new sessionId but leaves every previously issued identifier valid for authenticated web and API requests. Exploitation requires a stolen or leaked identifier and network access to the HTTP(S) service, granting the compromised account's permissions without its credentials.
Summary
What happened
Insufficient session expiration in Graylog Web Interface 2.2.3 allows remote attackers to access accounts with an old session identifier. Each successful login creates a new sessionId but leaves every previously issued identifier valid for authenticated web and API requests. Exploitation requires a stolen or leaked identifier and network access to the HTTP(S) service, granting the compromised account's permissions without its credentials.
The record
- CVE
- CVE-2026-1435
- Published
- Feb 18, 2026
- Updated
- Feb 18, 2026
- Vendor
- Graylog
- Product
- Graylog Web Interface
- Classifications
- CWE-613, T1550.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 18, 2026CVE publishedPublication date reported by the CVE source.
- Feb 18, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.2.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo