CVE-2026-55867

MEDIUMPre-NVD 5.35.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6% (45th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
5.3EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 5.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.3MEDIUMmedium confidence
EG Risk
24
EG Risk 24/100

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 (value × EchelonGraph’s weight)
Severity53% × 45%
The EG Score, 5.3 of 10.
Exploitation0.6% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.6%
EPSS %ILE
45th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 28, 2026

Last Modified

September 9, 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 pull request

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 pull request

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 pull request

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 pull request

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 advisoryMentions a patch (unverified)

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.

Affected Packages

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFix by version rangeDependents
org.graylog2:graylog2-server7.1.1
  • 6.2.0 up to 6.3.12: fixed in 6.3.12
  • 7.0.0 up to 7.0.7: fixed in 7.0.7
  • 7.1.0 up to 7.1.2: fixed in 7.1.2
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 14× in last 7d / 55× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  2. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  3. 2026-10-12 15:55 UTCEG score recompute
  4. 2026-10-11 19:38 UTCEG score recompute
  5. 2026-10-11 16:53 UTCEG score recompute
  6. 2026-10-11 14:16 UTCEG score recompute
  7. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  9. 2026-10-10 01:41 UTCEG score recompute
  10. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  11. 2026-10-09 02:36 UTCEG score recompute
  12. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  13. 2026-10-08 00:47 UTCEG score recompute
  14. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  15. 2026-10-06 23:51 UTCEG score recompute
  16. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  17. 2026-10-06 00:47 UTCEG score recompute
  18. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  19. 2026-10-05 01:20 UTCEG score recompute
  20. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  21. 2026-10-04 01:53 UTCEG score recompute
  22. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  23. 2026-10-03 02:44 UTCEG score recompute
  24. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  25. 2026-10-02 03:39 UTCEG score recompute
Show 59 more
  1. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  2. 2026-10-01 03:56 UTCEG score recompute
  3. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  4. 2026-09-30 04:52 UTCEG score recompute
  5. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  6. 2026-09-29 05:18 UTCEG score recompute
  7. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  8. 2026-09-28 06:12 UTCEG score recompute
  9. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  10. 2026-09-27 07:08 UTCEG score recompute
  11. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  12. 2026-09-26 08:02 UTCEG score recompute
  13. 2026-09-25 06:46 UTCEG score recompute
  14. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  15. 2026-09-24 07:41 UTCEG score recompute
  16. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  17. 2026-09-23 08:37 UTCEG score recompute
  18. 2026-09-22 09:32 UTCEG score recompute
  19. 2026-09-21 10:21 UTCEG score recompute
  20. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  21. 2026-09-20 11:16 UTCEG score recompute
  22. 2026-09-19 12:11 UTCEG score recompute
  23. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  24. 2026-09-18 13:04 UTCEG score recompute
  25. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  26. 2026-09-16 14:54 UTCEG score recompute
  27. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  28. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  29. 2026-09-15 15:41 UTCEG score recompute
  30. 2026-09-15 03:11 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  31. 2026-09-13 17:31 UTCEG score recompute
  32. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  33. 2026-09-12 18:26 UTCEG score recompute
  34. 2026-09-11 19:21 UTCEG score recompute
  35. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  36. 2026-09-10 20:16 UTCEG score recompute
  37. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  38. 2026-09-09 00:25 UTCEG score recompute
  39. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  40. 2026-09-07 16:04 UTCEG score recompute
  41. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  42. 2026-09-06 16:59 UTCEG score recompute
  43. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  44. 2026-09-05 17:54 UTCEG score recompute
  45. 2026-09-04 18:43 UTCEG score recompute
  46. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  47. 2026-09-02 20:23 UTCEG score recompute
  48. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  49. 2026-09-01 18:35 UTCEG score recompute
  50. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  51. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  52. 2026-08-31 19:29 UTCEG score recompute
  53. 2026-08-31 18:54 UTCEG score recompute
  54. 2026-08-30 21:35 UTCEG score recompute
  55. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  56. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  57. 2026-08-28 23:25 UTCEG score recompute
  58. 2026-08-28 22:22 UTCEG score recomputeFirst assessed: 5.3 MEDIUM
  59. 2026-08-28 22:18 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-55867?
CVE-2026-55867 is a medium-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-55867 published?
The CVE record for CVE-2026-55867 was published on August 28, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 9, 2026; the record at its source may have been updated since.
Is CVE-2026-55867 actively exploited?
CVE-2026-55867 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (45th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-55867?
CVE-2026-55867 has a CVSS base score of 5.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-55867?
A fix for CVE-2026-55867 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-55867 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by 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.

Book a Demo →Browse All CVEs