Graylog2 Server before commit 46a2eeb contains a missing per-entity permission check in the POST ...
Summary
Vulnerability reported (CVE-2026-65011). Risk of unauthorized operations or information disclosure. Exploitable via POST /events/definitions/{definitionId}/duplicate.
Original description
The description as published by the source.
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 event definitions including detection queries, aggregation thresholds, grouping fields, schedules, and notification bindings by duplicating them.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-65011 has been found.
Attackers can target a specific entry point like POST /events/definitions/{definitionId}/duplicate over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.3/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "CVE-2026-65011" on the vendor's site.
CVE-2026-65011 — CWE-862 / CVSS v3 4.3
Attack vector: remote (network-reachable) / no user interaction
Attack surface: POST /events/definitions/{definitionId}/duplicate
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-862) has been reported. Attackers reach the vulnerable code path via POST /events/definitions/{definitionId}/duplicate.
Check the vendor advisory for the affected versions. Attack surface: POST /events/definitions/{definitionId}/duplicate.
Severity: Medium (CVSS 4.3/10). Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual POST /events/definitions/{definitionId}/duplicate requests with malformed payloads or SQL meta-characters. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで影響コンポーネントを特定する。
-
2Hunt for indicators of compromise detect
grep 'POST /events/definitions/{definitionId}/duplicate' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /events/definitions/{definitionId}/duplicateへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Post-deployment verification verify
Replay attack against POST /events/definitions/{definitionId}/duplicate on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
References
- advisory nvd.nist.gov
- advisory vulncheck.com
- advisory github.com
- package github.com
- patch github.com
- patch github.com
- patch github.com
- patch github.com
- report github.com
- web github.com