Skip to content
Fencer Intel
medium 5.3

CVE-2026-33463 json

Operation on a Resource after Expiration or Termination in Kibana Leading to Unauthorized File Access

published 5mo ago modified 26d ago also BIT-elk-2026-33463 , BIT-kibana-2026-33463 , EUVD-2026-33011

cvss
5.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 14%
public exploits
0
none known

Summary

Operation 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.

Patch / fix

  • bitnami elk 8.19.16, 9.3.5
  • bitnami kibana 8.19.16, 9.3.5
  • elastic kibana 8.19.16, 9.3.5
  • elasticsearch kibana 8.19.16, 9.3.5

Is CVE-2026-33463 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
5mo ago

Exploit prediction

0.24% chance of exploitation in the next 30 days, higher than 14% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OSV 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Affected packages

ecosystem package affected fixed in
bitnami elk
>=8.0.0, <8.19.16
>=9.0.0, <9.3.5
8.19.16
9.3.5
bitnami kibana
>=8.0.0, <8.19.16
>=9.0.0, <9.3.5
8.19.16
9.3.5

Affected products

  • Elastic Kibana

Classification

Weakness
  • CWE-672 Operation on a Resource after Expiration or Release

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.