CVE-2026-55221: Boruta: OAuth credentials exposed in Boruta business logs
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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Borutato a version that resolves this vulnerability.Fixed in 0.10.0
Event History
Frequently Asked Questions
Who can exploit the exposed credentials?
Anyone who can access Boruta business logs, a log aggregation system receiving those logs, or the administration log viewer may be able to recover OAuth or OpenID Connect credentials. The attacker does not need to interact with the authorization endpoints if they can obtain the logged values.
Are credentials still usable after they are recovered from logs?
Recovered access tokens, refresh tokens, authorization codes, agent tokens, direct-post codes, ID tokens, VP tokens, and tokens sent to introspection or revocation endpoints may be usable until they expire or are revoked.
What should be done if an affected instance cannot be upgraded immediately?
Restrict access to Boruta logs, log aggregation systems, and the administration log viewer to reduce exposure. Treat credentials present in accessible historical logs as potentially disclosed and revoke them where possible.
How can I determine whether my deployment is affected?
Boruta versions prior to 0.10.0 are affected. Review business event logs for OAuth or OpenID Connect values such as tokens, authorization codes, or values submitted to introspection and revocation endpoints.