Skip to main content
VulnerabilityPublished

CVE-2026-1437: Graylog Web Interface · XSS or 'Cross-site Scripting'

Affects Graylog Web InterfaceSource CVE Database V5

0

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 09:16 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 15% 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:P/VC:L/VI:L/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. Weaponised: 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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
GraylogGraylog Web InterfaceAffected
  • =2.2.3
Fixed in–

AI-suggested

Given the absence of an official patch, European organizations should implement immediate compensating controls. First, restrict access to the Graylog web interface to trusted internal networks or VPNs to reduce exposure. Implement web application firewalls (WAFs) with custom rules to detect and block suspicious URL patterns targeting the '/system/authentication/users/edit/' endpoint. Educate users and administrators about the risk of clicking untrusted links, especially those purporting to be related to Graylog. Monitor web server logs for unusual requests containing suspicious scripts or encoded payloads. If possible, upgrade Graylog to a later version where this vulnerability is addressed or apply vendor-provided patches once available. Additionally, consider implementing Content Security Policy (CSP) headers to limit the execution of inline scripts and reduce the impact of XSS attacks. Regularly audit and review user privileges within Graylog to minimize potential damage from compromised sessions.

Description

Reflected Cross-Site Scripting (XSS) vulnerability in the Graylog Web Interface console, version 2.2.3, caused by a lack of proper sanitization and escaping in HTML output. Several endpoints include segments of the URL directly in the response without applying output encoding, allowing an attacker to inject and execute arbitrary JavaScript code when a user visits a specially crafted URL. Exploitation of this vulnerability may allow script execution in the victim's browser and limited manipulation of the affected user's session context, through the '/system/authentication/users/edit/' endpoint.

References

Community reviews

Loading reviews…