Graylog2__graylog2-server_CVE-2023-41044_5-1-2

Graylog 欢迎！ Graylog 是一个开源日志管理平台。 您可以在我们的官方网站上了解更多项目信息，并在文档站点查阅文档。 问题追踪 发现了一个 Bug？有改进的想法？欢迎提交问题。 贡献 帮助我们构建日志管理的未来，并参与到一个每天被成千上万人使用的项目中。 请遵循贡献者指南并阅读贡献说明以开始。 想要获得报酬来开发我们的开源产品？申请我们的职位！ 保持联系 欢迎加入 freenode IRC 上的 graylog 频道、libera 上的 graylog 频道，或在我们的社区论坛中创建话题与我们聊天。 许可证 Graylog 基于 服务器端公共许可证 SSPL 的第 1 版发...

CVE-2026-65011

Graylog2 Server before commit 46a2eeb contains a missing per-entity permission check in the POST /events/definitions/definitionId/duplicate endpoint that allows authenticated users to clone any event definition. Attackers with the low-privilege eventdefinitions:create capability can read private...

CVE-2026-65011 Graylog2 Server Missing Permission Check on Event Definition Duplicate

Graylog2 Server before commit 46a2eeb contains a missing per-entity permission check in the POST /events/definitions/definitionId/duplicate endpoint that allows authenticated users to clone any event definition. Attackers with the low-privilege eventdefinitions:create capability can read private...

CVE-2026-65011

Technical details are not publicly available in the provided documents. Monitor for updates.

Cross-site Scripting (XSS)

org.graylog2:graylog2-server is vulnerable to Cross-site Scripting XSS. The vulnerability is due to insecure input handling due to the ability to inject and submit malicious HTML forms via the Event Definition Remediation Step field, which can result in session cookie theft under specific...

Authentication Bypass

org.graylog2, graylog2-server is vulnerable to Authentication Bypass. The vulnerability is due to HTTP Inputs not correctly rejecting messages when a specified header is missing or has an incorrect value, allowing the message to be ingested despite returning a 401 HTTP response...

DNS Cache Poisoning

graylog2-server is vulnerable to DNS Cache Poisoning. The vulnerability exists because the library uses a single source port for DNS queries, leading to cache poisoning attacks...

Session Fixation

graylog2-server is vulnerable to Session Fixation. The vulnerability exists because a node may still have the session cached even when a user has explicitly logged out, which allows the session to still be used for API requests until it has reached its original expiry time...