# CVE-2026-33584: Arqit SKA-Platform Enables Access to Debug Information

> Unauthorized access to exposed Keycloak management service allows attackers to read sensitive debug information, metrics, and health data.

- **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:** No
- **Published:** 13 May 2026
- **Updated:** 13 May 2026
- **Also known as:** GHSA-7rhj-w7pg-37v4

## What is CVE-2026-33584?

CVE-2026-33584 is a medium-severity vulnerability in Arqit Symmetric Key Agreement Platform, published on 13 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Exposed Keycloak management 
service in the Arqit Symmetric Key Agreement Platform enables unauthorized access to sensitive debug 
information such as metrics and
 health data. This issue affects Symmetric Key Agreement Platform: before 26.03.

Weakness: CWE-749 (Exposed Dangerous Method or Function)

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


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

No fix has been published for CVE-2026-33584 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-33584 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-33584 is a medium-severity vulnerability in Arqit Symmetric Key Agreement Platform, published on 13 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-33584 in the wild and no public exploit code.

Affected product: Arqit Symmetric Key Agreement Platform. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-33584/ (Markdown: https://insights.sbomify.com/CVE-2026-33584/index.md)
```

## Sources

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

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