KibanaApplication · Elastic
CVE-2026-33463
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedOperation on a Resource after Expiration or Termination (CWE-672) in Kibana can lead to unauthorized information disclosure. A logic error in how expiration timestamps were validated allowed a time-bounded access token to remain usable beyond its intended validity window, enabling an unauthenticated actor in possession of the token to retrieve the associated content after expiration.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA logic error in Kibana's token expiration validation allows time-bounded access tokens to remain usable after their intended expiry. An unauthenticated attacker with a previously-valid token can continue retrieving associated content after the token has technically expired, leading to unauthorized information disclosure.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
KibanaApplication
>= 8.0.0, < 8.19.16>= 9.0.0, < 9.3.5CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed Kibana versionRun 'bin/kibana --version' or check the 'package.json' file in the Kibana installation directory, or query the Kibana API at GET /api/statusAffected if The installed version is 8.0.0 through 8.19.15, or 9.0.0 through 9.3.4 (meaning it falls within the affected ranges < 8.19.16 or < 9.3.5)
-
Confirm token-based authentication is in useCheck if Kibana is configured to use native authentication or elasticsearch-native auth realms by reviewing kibana.yml for 'xpack.security.authc.domains' or 'elasticsearch.username' settings, or by checking for created API tokens in Kibana's security settingsAffected if Kibana uses native user authentication or has API tokens created, as the vulnerability affects token expiration validation for these authentication mechanisms
-
Review Kibana audit logs for post-expiration token usageExamine Kibana's audit logs (typically in logs/audit.json or via the audit endpoint) for authentication events where 'event.type' is 'authentication_successful' and the timestamp exceeds the token's 'token.expiration' metadataAffected if Audit logs show successful API calls using tokens after their documented expiration time has passed, indicating the vulnerability is being exploited or was present
A user is affected if their Kibana version falls within 8.0.0 to 8.19.15 or 9.0.0 to 9.3.4, they use Kibana's native token authentication, and expired tokens can successfully authenticate.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data8.19.169.3.5
Apply the vendor patch to fix the token expiration validation logic in Kibana, and rotate any potentially compromised tokens that may have been used beyond their validity window.
Fix this in Kibana
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-33463 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-33463 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data