dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2025-14443

MEDIUM · 6.4 CVSS v3.1 Published 2025-12-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable 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
A flaw was found in ose-openshift-apiserver. This vulnerability allows internal network enumeration, service discovery, limited information disclosure, and potential denial-of-service (DoS) through Server-Side Request Forgery (SSRF) due to missing IP address and network-range validation when processing user-supplied image references.

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 · moderate confidence

This is a Server-Side Request Forgery (SSRF) vulnerability in the OpenShift API server (ose-openshift-apiserver). The flaw allows attackers to make the API server request arbitrary URLs via user-supplied image references due to missing validation of IP addresses and network ranges, enabling internal network enumeration, service discovery, and potential denial-of-service.

MitigationApply the vendor patch for CVE-2025-14443 which adds proper IP address and network-range validation for image references; implement network segmentation to limit exposure of internal services.

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
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
None
Availability
Low

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

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. Confirm OpenShift API server is deployed
    Run 'oc get pods -n openshift-apiserver' to list the API server pods and verify they are running. Also check cluster status with 'oc cluster-info'.
    Affected if OpenShift API server is running and accessible without additional network isolation.
  2. Identify the API server component version
    Run 'oc get clusterversion' to retrieve the OpenShift version. Then query the API server operator with 'oc get pods -n openshift-apiserver-operator -o wide' to identify the exact ose-openshift-apiserver image version being used.
    Affected if The installed version predates the CVE-2025-14443 patch and falls within the affected OpenShift version range for this SSRF flaw.
  3. Verify if image import functionality is accessible
    Check if users can create or update ImageStream resources by reviewing RBAC with 'oc get rolebindings -n default | grep system:image'. Also test creating an ImageStream with an external registry URL to confirm the feature accepts user-supplied image references.
    Affected if Users or service accounts with rights to create or import ImageStreams can supply arbitrary registry URLs through image references.
  4. Inspect API server network policies
    Run 'oc get networkpolicies -n openshift-apiserver' to check if egress or ingress policies restrict the API server pod's network access. Review the policies to determine if internal network destinations are blocked.
    Affected if No network policies exist or existing policies permit the API server to reach internal network ranges (RFC 1918 addresses) based on image reference requests.
  5. Check for internal network exposure vectors
    Attempt a controlled test (in a dev environment) by importing an image from an internal IP address (e.g., http://10.0.0.1:8080/image) as an ImageStream to confirm the API server can initiate requests to internal IPs. Alternatively, review API server audit logs for patterns of image pulls to internal addresses.
    Affected if The API server successfully makes outbound HTTP requests to internal IP addresses when users provide them in image references, confirming the SSRF vector is present.

You are affected if the OpenShift API server is running, users can import image references, and no network segmentation blocks the API server from reaching internal IP addresses or ranges.

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

Apply the vendor patch for CVE-2025-14443 which adds proper IP address and network-range validation for image references; implement network segmentation to limit exposure of internal services.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-14443 — 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-14443 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