CVE-2026-33381: Users can generate Service Account tokens after permissions removal
When a user's access to mint tokens for a service account is revoked, it is sometimes still possible to do so for a few seconds after the event. The user will eventually lose access to do this.
Security readout for executives and security teams
Plain-English summary
Grafana OSS may briefly continue honoring a removed permission to create service-account tokens. During this few-second window, a previously authorized user could create a token after access was revoked, potentially preserving unauthorized access to sensitive systems or actions.
Executive priority
Prioritize normal security maintenance, with faster action where Grafana service accounts protect sensitive data or privileged operations. The narrow timing window reduces likelihood, but successful abuse could affect confidentiality and integrity. Escalate if suspicious token creation follows access revocation.
Technical view
CVE-2026-33381 is a time-limited authorization failure classified as CWE-284. Exploitation requires network access, high privileges, and favorable timing, with no user interaction. The supplied CVSS 3.1 score is 5.9, reflecting potentially high confidentiality and integrity impact but no stated availability impact.
Likely exposure
Exposure is limited to the listed Grafana OSS releases and users who previously held service-account token-minting permission. Risk occurs specifically during the few seconds after that permission is removed. The source bundle marks other versions unaffected by default but provides no affected version ranges beyond the named releases.
Exploitation context
The timing requirement and prior high privileges make exploitation difficult and situational. The supplied sources do not report active exploitation, and the CVE is not listed as KEV. They do not establish token lifetime, resulting access scope, or whether tokens minted during the window remain valid.
Researcher notes
The evidence supports a short authorization-consistency window after revocation. CVSS indicates AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N. The supplied material does not identify the underlying component, fixed versions, patch mechanism, exploit observations, token persistence, or detailed detection indicators; those points should remain unconfirmed.
Mitigation direction
Check Grafana's advisory for current remediation or upgrade guidance.
Restrict service-account token-minting permission to essential administrators.
Monitor token creation closely during and immediately after permission revocations.
Investigate and revoke unexpected service-account tokens using vendor-supported procedures.
Validation and detection
Inventory Grafana OSS deployments and record their exact versions.
Compare versions against every affected release listed in the CVE record.
Review available logs for token creation immediately after permission removal.
Confirm remediation status using Grafana's current security advisory.
Investigate unexpected tokens and verify their authorization and ownership.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-284: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
2Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-284 · source CWE mapping
Improper Access Control
Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.