Graylog Web Interface 2.2.3 /system/index_sets/ cross site scripting

Summaryinfo

A vulnerability classified as problematic has been found in Graylog Web Interface 2.2.3. The impacted element is an unknown function of the file /system/index_sets/. Performing a manipulation results in cross site scripting. This vulnerability is known as CVE-2026-1441. Remote exploitation of the attack is possible. No exploit is available.

Detailsinfo

A vulnerability, which was classified as problematic, was found in Graylog Web Interface 2.2.3. This affects some unknown processing of the file /system/index_sets/. The manipulation with an unknown input leads to a cross site scripting vulnerability. CWE is classifying the issue as CWE-79. The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. This is going to have an impact on integrity. The summary by CVE is:

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/index_sets/' endpoint.

The weakness was published by Julen Garrido Estévez. The advisory is shared at incibe.es. This vulnerability is uniquely identified as CVE-2026-1441 since 01/26/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1059.007 for this issue.

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