{"items":[{"id":"NVI-00013941","kind":"vulnerability","title":"Graylog token revocation endpoint allows authenticated users to delete other users’ access tokens","revision":3,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-j769-9gv9-65gr","CVE-2026-55867"],"plain_summary":"GitHub lists this reviewed advisory for org.graylog2:graylog2-server, org.graylog2:graylog2-server, org.graylog2:graylog2-server. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-06d7d1ba5aec787f257049c228b9d226"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-09-09T21:09:13.080Z","value":"5.3 MEDIUM (4.0)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-1d86891f4273deef6e654982c959c434"},{"kind":"EPSS","as_of":"2026-11-04T12:03:12.000Z","value":"0.565%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.47039. Missing scores are unknown.","source_id":"sr-06d7d1ba5aec787f257049c228b9d226"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-2160c20a6f1a714ff293f48e782b988c","url":"https://github.com/advisories/GHSA-j769-9gv9-65gr","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-j769-9gv9-65gr","publisher":"GitHub Advisory Database","observed_at":"2026-11-02T02:21:58.521Z"},{"id":"sr-1d86891f4273deef6e654982c959c434","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-55867","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-55867","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-08T01:48:33.286Z"},{"id":"sr-06d7d1ba5aec787f257049c228b9d226","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-55867","publisher":"FIRST EPSS","observed_at":"2026-11-04T23:33:33.051Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-2160c20a6f1a714ff293f48e782b988c"],"technology":"org.graylog2:graylog2-server","known_exclusions":[],"conditions_summary":"### Impact\n\nGraylog contains an insecure direct object reference (IDOR) vulnerability in the token revocation endpoint. An authenticated user can delete access tokens belonging to other users, including service account tokens and administrator tokens, if they know or can guess a valid token identifier.\n\nThe issue does not expose token contents, but it allows unauthorized token deletion, leading to integrity impact and potential availability impact for access token based integrations.\n\n### Patches\n\nThe issue has been fixed in the following Graylog versions: `6.3.12`, `7.0.7`, `7.1.2`. Users should upgrade to one of these versions or above to remediate the vulnerability.\n\nGraylog Cloud has already been patched.\n\n### Workarounds\n\nThere are no feasible workarounds for this issue. Upgrading to a patched version is recommended.\n\nCustomers using Graylog Enterprise or Security can review the audit log[^1] for suspicious activity. Audit log lines for successful token deletions begin with `access token deleted from user`. \n\n### Credits\n\nThanks to michaelddickenson and sreelim for reporting.\n\n\n[^1]: https://go2docs.graylog.","public_affected_ranges":[">= 6.2.0, < 6.3.12"]},{"certainty":"source_listed","source_ids":["sr-2160c20a6f1a714ff293f48e782b988c"],"technology":"org.graylog2:graylog2-server","known_exclusions":[],"conditions_summary":"### Impact\n\nGraylog contains an insecure direct object reference (IDOR) vulnerability in the token revocation endpoint. An authenticated user can delete access tokens belonging to other users, including service account tokens and administrator tokens, if they know or can guess a valid token identifier.\n\nThe issue does not expose token contents, but it allows unauthorized token deletion, leading to integrity impact and potential availability impact for access token based integrations.\n\n### Patches\n\nThe issue has been fixed in the following Graylog versions: `6.3.12`, `7.0.7`, `7.1.2`. Users should upgrade to one of these versions or above to remediate the vulnerability.\n\nGraylog Cloud has already been patched.\n\n### Workarounds\n\nThere are no feasible workarounds for this issue. Upgrading to a patched version is recommended.\n\nCustomers using Graylog Enterprise or Security can review the audit log[^1] for suspicious activity. Audit log lines for successful token deletions begin with `access token deleted from user`. \n\n### Credits\n\nThanks to michaelddickenson and sreelim for reporting.\n\n\n[^1]: https://go2docs.graylog.","public_affected_ranges":[">= 7.0.0, < 7.0.7"]},{"certainty":"source_listed","source_ids":["sr-2160c20a6f1a714ff293f48e782b988c"],"technology":"org.graylog2:graylog2-server","known_exclusions":[],"conditions_summary":"### Impact\n\nGraylog contains an insecure direct object reference (IDOR) vulnerability in the token revocation endpoint. An authenticated user can delete access tokens belonging to other users, including service account tokens and administrator tokens, if they know or can guess a valid token identifier.\n\nThe issue does not expose token contents, but it allows unauthorized token deletion, leading to integrity impact and potential availability impact for access token based integrations.\n\n### Patches\n\nThe issue has been fixed in the following Graylog versions: `6.3.12`, `7.0.7`, `7.1.2`. Users should upgrade to one of these versions or above to remediate the vulnerability.\n\nGraylog Cloud has already been patched.\n\n### Workarounds\n\nThere are no feasible workarounds for this issue. Upgrading to a patched version is recommended.\n\nCustomers using Graylog Enterprise or Security can review the audit log[^1] for suspicious activity. Audit log lines for successful token deletions begin with `access token deleted from user`. \n\n### Credits\n\nThanks to michaelddickenson and sreelim for reporting.\n\n\n[^1]: https://go2docs.graylog.","public_affected_ranges":[">= 7.1.0, < 7.1.2"]}],"null_published_at":"2026-11-08T19:53:44.034Z","source_updated_at":"2026-08-28T22:15:42.000Z","source_disclosed_at":"2026-08-28T22:15:41.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Source facts changed; compare the preserved prior revision.","null_first_observed_at":"2026-11-02T02:21:58.521Z"},{"id":"NVI-00013941","kind":"vulnerability","title":"Graylog token revocation endpoint allows authenticated users to delete other users’ access tokens","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-j769-9gv9-65gr","CVE-2026-55867"],"plain_summary":"GitHub lists this reviewed advisory for org.graylog2:graylog2-server, org.graylog2:graylog2-server, org.graylog2:graylog2-server. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-06d7d1ba5aec787f257049c228b9d226"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"EPSS","as_of":"2026-11-04T12:03:12.000Z","value":"0.565%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.47039. Missing scores are unknown.","source_id":"sr-06d7d1ba5aec787f257049c228b9d226"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-2160c20a6f1a714ff293f48e782b988c","url":"https://github.com/advisories/GHSA-j769-9gv9-65gr","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-j769-9gv9-65gr","publisher":"GitHub Advisory Database","observed_at":"2026-11-02T02:21:58.521Z"},{"id":"sr-06d7d1ba5aec787f257049c228b9d226","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-55867","publisher":"FIRST EPSS","observed_at":"2026-11-04T23:33:33.051Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-2160c20a6f1a714ff293f48e782b988c"],"technology":"org.graylog2:graylog2-server","known_exclusions":[],"conditions_summary":"### Impact\n\nGraylog contains an insecure direct object reference (IDOR) vulnerability in the token revocation endpoint. An authenticated user can delete access tokens belonging to other users, including service account tokens and administrator tokens, if they know or can guess a valid token identifier.\n\nThe issue does not expose token contents, but it allows unauthorized token deletion, leading to integrity impact and potential availability impact for access token based integrations.\n\n### Patches\n\nThe issue has been fixed in the following Graylog versions: `6.3.12`, `7.0.7`, `7.1.2`. Users should upgrade to one of these versions or above to remediate the vulnerability.\n\nGraylog Cloud has already been patched.\n\n### Workarounds\n\nThere are no feasible workarounds for this issue. Upgrading to a patched version is recommended.\n\nCustomers using Graylog Enterprise or Security can review the audit log[^1] for suspicious activity. Audit log lines for successful token deletions begin with `access token deleted from user`. \n\n### Credits\n\nThanks to michaelddickenson and sreelim for reporting.\n\n\n[^1]: https://go2docs.graylog.","public_affected_ranges":[">= 6.2.0, < 6.3.12"]},{"certainty":"source_listed","source_ids":["sr-2160c20a6f1a714ff293f48e782b988c"],"technology":"org.graylog2:graylog2-server","known_exclusions":[],"conditions_summary":"### Impact\n\nGraylog contains an insecure direct object reference (IDOR) vulnerability in the token revocation endpoint. An authenticated user can delete access tokens belonging to other users, including service account tokens and administrator tokens, if they know or can guess a valid token identifier.\n\nThe issue does not expose token contents, but it allows unauthorized token deletion, leading to integrity impact and potential availability impact for access token based integrations.\n\n### Patches\n\nThe issue has been fixed in the following Graylog versions: `6.3.12`, `7.0.7`, `7.1.2`. Users should upgrade to one of these versions or above to remediate the vulnerability.\n\nGraylog Cloud has already been patched.\n\n### Workarounds\n\nThere are no feasible workarounds for this issue. Upgrading to a patched version is recommended.\n\nCustomers using Graylog Enterprise or Security can review the audit log[^1] for suspicious activity. Audit log lines for successful token deletions begin with `access token deleted from user`. \n\n### Credits\n\nThanks to michaelddickenson and sreelim for reporting.\n\n\n[^1]: https://go2docs.graylog.","public_affected_ranges":[">= 7.0.0, < 7.0.7"]},{"certainty":"source_listed","source_ids":["sr-2160c20a6f1a714ff293f48e782b988c"],"technology":"org.graylog2:graylog2-server","known_exclusions":[],"conditions_summary":"### Impact\n\nGraylog contains an insecure direct object reference (IDOR) vulnerability in the token revocation endpoint. An authenticated user can delete access tokens belonging to other users, including service account tokens and administrator tokens, if they know or can guess a valid token identifier.\n\nThe issue does not expose token contents, but it allows unauthorized token deletion, leading to integrity impact and potential availability impact for access token based integrations.\n\n### Patches\n\nThe issue has been fixed in the following Graylog versions: `6.3.12`, `7.0.7`, `7.1.2`. Users should upgrade to one of these versions or above to remediate the vulnerability.\n\nGraylog Cloud has already been patched.\n\n### Workarounds\n\nThere are no feasible workarounds for this issue. Upgrading to a patched version is recommended.\n\nCustomers using Graylog Enterprise or Security can review the audit log[^1] for suspicious activity. Audit log lines for successful token deletions begin with `access token deleted from user`. \n\n### Credits\n\nThanks to michaelddickenson and sreelim for reporting.\n\n\n[^1]: https://go2docs.graylog.","public_affected_ranges":[">= 7.1.0, < 7.1.2"]}],"null_published_at":"2026-11-06T07:24:11.269Z","source_updated_at":"2026-08-28T22:15:42.000Z","source_disclosed_at":"2026-08-28T22:15:41.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-11-02T02:21:58.521Z"},{"id":"NVI-00013941","kind":"vulnerability","title":"Graylog token revocation endpoint allows authenticated users to delete other users’ access tokens","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-j769-9gv9-65gr","CVE-2026-55867"],"plain_summary":"GitHub lists this reviewed advisory for org.graylog2:graylog2-server, org.graylog2:graylog2-server, org.graylog2:graylog2-server. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-2160c20a6f1a714ff293f48e782b988c"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-2160c20a6f1a714ff293f48e782b988c","url":"https://github.com/advisories/GHSA-j769-9gv9-65gr","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-j769-9gv9-65gr","publisher":"GitHub Advisory Database","observed_at":"2026-11-02T02:21:58.521Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-2160c20a6f1a714ff293f48e782b988c"],"technology":"org.graylog2:graylog2-server","known_exclusions":[],"conditions_summary":"### Impact\n\nGraylog contains an insecure direct object reference (IDOR) vulnerability in the token revocation endpoint. An authenticated user can delete access tokens belonging to other users, including service account tokens and administrator tokens, if they know or can guess a valid token identifier.\n\nThe issue does not expose token contents, but it allows unauthorized token deletion, leading to integrity impact and potential availability impact for access token based integrations.\n\n### Patches\n\nThe issue has been fixed in the following Graylog versions: `6.3.12`, `7.0.7`, `7.1.2`. Users should upgrade to one of these versions or above to remediate the vulnerability.\n\nGraylog Cloud has already been patched.\n\n### Workarounds\n\nThere are no feasible workarounds for this issue. Upgrading to a patched version is recommended.\n\nCustomers using Graylog Enterprise or Security can review the audit log[^1] for suspicious activity. Audit log lines for successful token deletions begin with `access token deleted from user`. \n\n### Credits\n\nThanks to michaelddickenson and sreelim for reporting.\n\n\n[^1]: https://go2docs.graylog.","public_affected_ranges":[">= 6.2.0, < 6.3.12"]},{"certainty":"source_listed","source_ids":["sr-2160c20a6f1a714ff293f48e782b988c"],"technology":"org.graylog2:graylog2-server","known_exclusions":[],"conditions_summary":"### Impact\n\nGraylog contains an insecure direct object reference (IDOR) vulnerability in the token revocation endpoint. An authenticated user can delete access tokens belonging to other users, including service account tokens and administrator tokens, if they know or can guess a valid token identifier.\n\nThe issue does not expose token contents, but it allows unauthorized token deletion, leading to integrity impact and potential availability impact for access token based integrations.\n\n### Patches\n\nThe issue has been fixed in the following Graylog versions: `6.3.12`, `7.0.7`, `7.1.2`. Users should upgrade to one of these versions or above to remediate the vulnerability.\n\nGraylog Cloud has already been patched.\n\n### Workarounds\n\nThere are no feasible workarounds for this issue. Upgrading to a patched version is recommended.\n\nCustomers using Graylog Enterprise or Security can review the audit log[^1] for suspicious activity. Audit log lines for successful token deletions begin with `access token deleted from user`. \n\n### Credits\n\nThanks to michaelddickenson and sreelim for reporting.\n\n\n[^1]: https://go2docs.graylog.","public_affected_ranges":[">= 7.0.0, < 7.0.7"]},{"certainty":"source_listed","source_ids":["sr-2160c20a6f1a714ff293f48e782b988c"],"technology":"org.graylog2:graylog2-server","known_exclusions":[],"conditions_summary":"### Impact\n\nGraylog contains an insecure direct object reference (IDOR) vulnerability in the token revocation endpoint. An authenticated user can delete access tokens belonging to other users, including service account tokens and administrator tokens, if they know or can guess a valid token identifier.\n\nThe issue does not expose token contents, but it allows unauthorized token deletion, leading to integrity impact and potential availability impact for access token based integrations.\n\n### Patches\n\nThe issue has been fixed in the following Graylog versions: `6.3.12`, `7.0.7`, `7.1.2`. Users should upgrade to one of these versions or above to remediate the vulnerability.\n\nGraylog Cloud has already been patched.\n\n### Workarounds\n\nThere are no feasible workarounds for this issue. Upgrading to a patched version is recommended.\n\nCustomers using Graylog Enterprise or Security can review the audit log[^1] for suspicious activity. Audit log lines for successful token deletions begin with `access token deleted from user`. \n\n### Credits\n\nThanks to michaelddickenson and sreelim for reporting.\n\n\n[^1]: https://go2docs.graylog.","public_affected_ranges":[">= 7.1.0, < 7.1.2"]}],"null_published_at":"2026-11-02T10:00:37.177Z","source_updated_at":"2026-08-28T22:15:42.000Z","source_disclosed_at":"2026-08-28T22:15:41.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-11-02T02:21:58.521Z"}],"next_cursor":null,"snapshot_revision":"42594"}