# CVE-2025-25208: Rhcl: authorino denial of service through authpolicy with sharedsecretref severity

> A developer can cause a denial of service in Authorino by configuring an AuthPolicy with a shared secret reference, blocking policy evaluation.

- **Severity:** Medium 5.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 9 Jun 2025
- **Updated:** 26 Mar 2026
- **Also known as:** GHSA-vqvv-2wj5-q34w, GO-2025-3747

## What is CVE-2025-25208?

CVE-2025-25208 is a medium-severity denial of service vulnerability in Red Hat Connectivity Link 1, published on 9 Jun 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

A Developer persona can bring down the Authorino service, preventing the evaluation of all AuthPolicies on the cluster

Weakness: CWE-400 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2025-25208?

3 open source packages ship an affected version, including github.com/kuadrant/authorino.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/kuadrant/authorino` | Go | All versions | None |
| `github.com/kuadrant/authorino` | Go | All versions to 0.20.0 | None |
| `github.com/kuadrant/authorino` | Go | All versions to 0.20.0 | None |

## How do I fix CVE-2025-25208?

Upgrade to a fixed version.

## Is CVE-2025-25208 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-25208 and fix it if it is affected.

What it is: CVE-2025-25208 is a medium-severity denial of service vulnerability in Red Hat Connectivity Link 1, published on 9 Jun 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-25208 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/kuadrant/authorino (Go): affected all versions; no fix listed
- github.com/kuadrant/authorino (Go): affected all versions up to 0.20.0; no fix listed
- github.com/kuadrant/authorino (Go): affected all versions up to 0.20.0; no fix listed

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

## Sources

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

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