# CVE-2026-55221: Boruta: OAuth credentials exposed in Boruta business logs

> Attackers with log access can steal OAuth tokens and credentials from Boruta server logs, enabling unauthorized access until expiration.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Sep 2026
- **Updated:** 2 Sep 2026
- **Also known as:** GHSA-pqwf-v25h-4874

## What is CVE-2026-55221?

CVE-2026-55221 is a medium-severity vulnerability in malach-it boruta-server, published on 2 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Boruta is a standalone authorization server that aims to implement OAuth 2.0 and Openid Connect up to decentralized identity specifications. Prior to version 0.10.0, Boruta logged sensitive OAuth and OpenID Connect values in business event logs. Logged values could include access tokens, refresh tokens, authorization codes, agent tokens, direct-post codes, ID tokens, VP tokens, and tokens submitted to introspection or revocation endpoints. An attacker with access to Boruta logs, log aggregation systems, or the administration log viewer could recover these credentials and use them until expiration or revocation. This issue has been patched in version 0.10.0.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

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


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

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

## Is CVE-2026-55221 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-55221 is a medium-severity vulnerability in malach-it boruta-server, published on 2 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-55221 in the wild and no public exploit code.

Affected product: malach-it boruta-server. 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-55221/ (Markdown: https://insights.sbomify.com/CVE-2026-55221/index.md)
```

## Sources

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

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