CVE-2026-55867

MEDIUMPre-NVD 5.35.3
EchelonGraph scoreLOW confidence

This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: secondary
Trending — 3 sources updated this week
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.3Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Graylog is a free and open log management platform. From 6.2.0 until 6.3.12, 7.0.7, and 7.1.2, the DELETE /users/{userId}/tokens/{idOrToken} endpoint implemented by UsersResource.revokeToken() in graylog2-server/src/main/java/org/graylog2/rest/resources/users/UsersResource.java checks USERS_TOKENREMOVE permission against the attacker-controlled userId path parameter before resolving the token selected by idOrToken. An authenticated user can provide an authorized userId while accessTokenService.loadById() or accessTokenService.load() resolves a token belonging to another user, including a service account or administrator, after which accessTokenService.destroy() deletes that token without checking AccessToken.getUserName(). The issue does not expose token contents, but unauthorized deletion causes integrity impact and can disrupt access-token-based integrations. This issue is fixed in versions 6.3.12, 7.0.7, and 7.1.2.

CVSS v3
5.3
EG Score
5.3(low)
EG Risk
28(Track)
EG Risk 28/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity53% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
26%
KEV
Not listed

Published

August 28, 2026

Last Modified

August 28, 2026

Advisory Details (9)

Auto-updated Aug 28, 2026
Patch available. Sources: github_pr, github_commit, github.
github_commit

commit e5accc5f4ce4 (Graylog2/graylog2-server)

Fix landed in Graylog2/graylog2-server commit e5accc5f4ce4 — awaiting tagged release

https://github.com/Graylog2/graylog2-server/commit/e5accc5f4ce48bd61b84bb8e5a13d21f8eac3da5
github_commit

commit 84b0ffa0bdf9 (Graylog2/graylog2-server)

Fix landed in Graylog2/graylog2-server commit 84b0ffa0bdf9 — awaiting tagged release

https://github.com/Graylog2/graylog2-server/commit/84b0ffa0bdf918f6edd2bb23a47254088634b1fc
github_commit

commit 4f280138b53d (Graylog2/graylog2-server)

Fix landed in Graylog2/graylog2-server commit 4f280138b53d — awaiting tagged release

https://github.com/Graylog2/graylog2-server/commit/4f280138b53dc3bbb5749213e8cb1c8e372f23a2
github_commit

commit 41d3745d0e52 (Graylog2/graylog2-server)

Fix landed in Graylog2/graylog2-server commit 41d3745d0e52 — awaiting tagged release

https://github.com/Graylog2/graylog2-server/commit/41d3745d0e52736d06c07d279ca0d72c1616df4c
github_pr

Fix revoke token ownership (`6.3`)

Fix merged in Graylog2/graylog2-server PR #26055 on 2026-05-19 — awaiting tagged release

https://github.com/Graylog2/graylog2-server/pull/26055
github_pr

Fix revoke token ownership (`7.0`)

Fix merged in Graylog2/graylog2-server PR #26053 on 2026-05-19 — awaiting tagged release

https://github.com/Graylog2/graylog2-server/pull/26053
github_pr

Fix revoke token ownership (`7.1`)

Fix merged in Graylog2/graylog2-server PR #26051 on 2026-05-19 — awaiting tagged release

https://github.com/Graylog2/graylog2-server/pull/26051
github_pr

Fix revoke token ownership

Fix merged in Graylog2/graylog2-server PR #26049 on 2026-05-19 — awaiting tagged release

https://github.com/Graylog2/graylog2-server/pull/26049
github Patch Available

Graylog token revocation endpoint allows authenticated users to delete other users’ access tokens · Advisory · Graylog2/graylog2-server · GitHub

https://github.com/Graylog2/graylog2-server/security/advisories/GHSA-j769-9gv9-65gr

Vendor Advisories for CVE-2026-55867(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 4× in last 7d / 4× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-30 01:22 UTCEPSS rescore
  2. 2026-08-28 23:25 UTCEG score recompute
  3. 2026-08-28 22:22 UTCEG score recompute
  4. 2026-08-28 22:18 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-55867?
CVE-2026-55867 is a medium vulnerability published on August 28, 2026. Graylog is a free and open log management platform. From 6.2.0 until 6.3.12, 7.0.7, and 7.1.2, the DELETE /users/{userId}/tokens/{idOrToken} endpoint implemented by UsersResource.revokeToken() in graylog2-server/src/main/java/org/graylog2/rest/resources/users/UsersResource.java checks…
When was CVE-2026-55867 disclosed?
CVE-2026-55867 was first published in the National Vulnerability Database on August 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-55867 actively exploited?
CVE-2026-55867 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 73.9% of all scored CVEs.
What is the CVSS score of CVE-2026-55867?
CVE-2026-55867 has a CVSS v3 base score of 5.3 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-55867?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-55867, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-55867

Explore →

Is Your Infrastructure Affected by CVE-2026-55867?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs