# CVE-2026-33463: Operation on a Resource after Expiration or Termination in Kibana Leading to Unauthorized File Access

> An attacker with an expired token can bypass expiration checks to access unauthorized content in Kibana.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 May 2026
- **Updated:** 29 May 2026
- **Also known as:** BIT-elk-2026-33463, BIT-kibana-2026-33463, GHSA-fgvg-65vf-2w8h, MINI-2v22-454q-w284, MINI-46wq-cxcf-p73f, MINI-6pj2-vw29-wm4h, MINI-r5vq-q5gj-qwqw, MINI-vh3h-jwwm-pw9x, MINI-wmfr-3jr3-xcfc

## What is CVE-2026-33463?

CVE-2026-33463 is a medium-severity authentication bypass vulnerability in Elastic Kibana, published on 28 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-672 (Operation on a Resource after Expiration or Release)

## Which versions are affected by CVE-2026-33463?

2 open source packages ship an affected version, including kibana and elk. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `kibana` | Bitnami | From 8.0.0 | 8.19.16, 9.3.5 |
| `elk` | Bitnami | From 8.0.0 | 8.19.16, 9.3.5 |

Products: Elastic Kibana.

## How do I fix CVE-2026-33463?

Upgrade kibana to a fixed version for your release line: 8.19.16 or 9.3.5.

## Is CVE-2026-33463 being exploited?

There is no known exploitation of CVE-2026-33463 in the wild and no public exploit code.

## Other vulnerabilities in Elastic Kibana

- [CVE-2019-7609](https://insights.sbomify.com/CVE-2019-7609/): Kibana Arbitrary Code Execution (critical 9.8, exploited in the wild)
- [CVE-2025-25015](https://insights.sbomify.com/CVE-2025-25015/): Kibana arbitrary code execution via prototype pollution (critical 9.9)
- [CVE-2024-37288](https://insights.sbomify.com/CVE-2024-37288/): Deserialization in Kibana (critical 9.9)
- [CVE-2023-31415](https://insights.sbomify.com/CVE-2023-31415/): Code injection in Kibana (critical 9.9)
- [CVE-2018-17245](https://insights.sbomify.com/CVE-2018-17245/): Information disclosure in Kibana (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-33463 and fix it if it is affected.

What it is: CVE-2026-33463 is a medium-severity authentication bypass vulnerability in Elastic Kibana, published on 28 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-33463 in the wild and no public exploit code.

Affected packages and fixed versions:
- kibana (Bitnami): affected from 8.0.0; fixed in 8.19.16, 9.3.5
- elk (Bitnami): affected from 8.0.0; fixed in 8.19.16, 9.3.5

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-33463/ (Markdown: https://insights.sbomify.com/CVE-2026-33463/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-33463
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-33463
- OSV: https://osv.dev/vulnerability/CVE-2026-33463

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-33463/
Summaries are generated and may contain mistakes; the official description above is the record.