VulnerabilityPublished 28 May 2026

CVE-2026-33463: Elastic Kibana · Operation on a Resource after Expiration or Release

Affects Elastic KibanaSource CVE Database V5

Compare

Not known to be exploited · CVSS 5.3 Medium.

Data as of 29 Oct 2026, 19:04 UTC

CVSS 3.1 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 14% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 28 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
ElasticKibana	Affected >=8.0.0 <=8.19.15 >=9.0.0 <=9.3.4	Fixed in–

AI-suggested

Until a patch is available, restrict token distribution and consider reducing token lifetime where possible to minimize exposure.

Description

CVE-2026-33463 is a medium severity vulnerability in Elastic Kibana versions 8.0.0 and 9.0.0 involving a logic error in expiration timestamp validation. This flaw allows a time-bounded access token to be used beyond its intended validity period, enabling an unauthenticated actor with the token to access associated content after expiration. The vulnerability is categorized as CWE-672, an operation on a resource after expiration or termination. There is no indication of known exploits in the wild or an official patch at this time.

Impact

An unauthenticated attacker in possession of an expired time-bounded access token can retrieve content that should no longer be accessible, resulting in unauthorized information disclosure. There is no impact on integrity or availability reported. The vulnerability does not require privileges or user interaction to exploit.

Summary

This vulnerability in Elastic Kibana arises from improper validation of expiration timestamps for access tokens. Due to a logic error, tokens that should have expired remain usable, allowing unauthorized information disclosure by unauthenticated actors possessing such tokens. The issue affects Kibana versions 8.0.0 and 9.0.0. The CVSS 3.1 base score is 5.3, reflecting a network attack vector with low complexity, no privileges or user interaction required, and limited confidentiality impact. No official remediation or patch has been documented, and this is not a cloud service vulnerability.

References

discuss.elastic.co/t/8-19-16-9-3-5-security-update-esa-2026-33/386551 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 4 Jun 2026, 20:54 UTC

WeaknessesCWE-672

Technical details

References

Community reviews

Related threats