dbcve.org
Resource Allocation Without LimitsWeakness · CWE-770

CVE-2025-25207

MEDIUM · 5.7 CVSS v3.1 Published 2025-06-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The Authorino service in the Red Hat Connectivity Link is the authorization service for zero trust API security. Authorino allows the users with developer persona to add callbacks to be executed to HTTP endpoints once the authorization process is completed. It was found that an attacker with developer persona access can add a large number of those callbacks to be executed by Authorino and as the authentication policy is enforced by a single instance of the service, this leada to a Denial of Service in Authorino while processing the post-authorization callbacks.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Authorino authorization service in Red Hat Connectivity Link lacks rate limiting on callback registration, allowing users with developer persona to register an unlimited number of post-authorization HTTP callbacks. Since the authentication policy is enforced by a single service instance that processes callbacks sequentially, the large volume of registered callbacks exhausts resources and causes Denial of Service.

MitigationImplement rate limiting on callback registration per user/policy, and horizontally scale or cluster the Authorino service to handle callback processing load without single-point-of-failure resource exhaustion.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Adjacent
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Authorino service is deployed
    Check for Authorino pods or services in the Kubernetes/OpenShift cluster: 'kubectl get pods -A | grep authorino' or 'oc get pods -A | grep -i authorino'
    Affected if Authorino is not found in the environment, the vulnerability does not apply
  2. Check callback registration endpoint access
    Verify if developer persona users have access to the callback registration API endpoint. Review RBAC policies or API access controls that govern who can create/update callback resources in the Authorino namespace
    Affected if Developer persona users can access callback registration APIs without rate limiting constraints
  3. Inspect rate limiting configuration on callback registration
    Check Authorino custom resources for rate limiting policies on callback registration. Look for RateLimitPolicy or similar CRDs applied to the callback registration endpoint
    Affected if No rate limiting policy exists specifically for callback registration endpoints
  4. Enumerate registered callbacks per policy
    Query Authorino for the number of callbacks registered: 'kubectl get authorization -A -o jsonpath={..spec.callbacks}' or review the Authorino CRDs to count callback objects linked to each authorization policy
    Affected if A single policy or user has registered an excessive number of callbacks (hundreds to thousands) indicating resource exhaustion potential
  5. Verify Authorino deployment scaling
    Check the number of Authorino replicas: 'kubectl get deployment authorino -n <namespace>' or 'oc get deployment authorino -n <namespace>'
    Affected if Only a single Authorino instance is running (replica count of 1) and callbacks are processed sequentially without horizontal scaling

If Authorino is deployed, developer users can access callback registration without restrictions, no rate limiting exists on that endpoint, and a single instance processes callbacks sequentially, the environment is vulnerable to resource exhaustion via excessive callback registration.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement rate limiting on callback registration per user/policy, and horizontally scale or cluster the Authorino service to handle callback processing load without single-point-of-failure resource exhaustion.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation20.0 h
  • Testing12.0 h
  • Review / QA8.0 h
46.0 hours of engineering $8,040
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,864.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-25207 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-25207 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data