dbcve.org
SatelliteApplication · Redhat

CVE-2025-9572

MEDIUM · 6.5 CVSS v3.1 Published 2026-02-27
Fix available
A fix is available. Upgrade to 3.16.2 or later.
See remediation →
71/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
n authorization flaw in Foreman's GraphQL API allows low-privileged users to access metadata beyond their assigned permissions. Unlike the REST API, which correctly enforces access controls, the GraphQL endpoint does not apply proper filtering, leading to an authorization bypass.

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

Foreman's GraphQL API fails to enforce authorization controls, allowing low-privileged users to access metadata beyond their assigned permissions. Unlike the REST API which properly filters data based on user permissions, the GraphQL endpoint does not apply the same access control filtering, resulting in an authorization bypass.

MitigationApply proper permission filtering to all GraphQL queries and mutations to match REST API authorization behavior. Until a patch is available, consider restricting or disabling GraphQL API access for low-privileged users.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
SatelliteApplication
Affected:= 6.15= 6.16= 6.17= 6.18
Satellite CapsuleApplication
Affected:= 6.15= 6.16= 6.17= 6.18
Enterprise LinuxOperating system
Affected:= 9.0
ForemanApplication
Affected:>= 1.22.0, < 3.16.2

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
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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. Check Foreman or Red Hat Satellite version
    Run 'foreman --version' or check the Satellite web UI under Administer > About. For Satellite, run 'satellite-installer --version' or check /etc/foreman/foreman-version
    Affected if Version is 1.22.0 through 3.16.1 (Theforeman Foreman), or 6.15, 6.16, 6.17, or 6.18 (Red Hat Satellite/Capsule), or RHEL 9.0 with vulnerable Foreman packages
  2. Confirm GraphQL API is accessible
    Attempt to access the /api/v2/graphql or /graphql endpoint on your Foreman/Satellite server using a web browser or curl
    Affected if The GraphQL endpoint returns a response (rather than 404 or authentication required)
  3. Identify low-privileged user accounts
    Log into the Foreman/Satellite web UI as an administrator, then navigate to Administer > Users to list accounts. Note users assigned roles with limited permissions (such as Viewer, Bookmarks, or custom roles with restricted resources)
    Affected if At least one user exists with limited permissions who should not have full access to all metadata
  4. Test GraphQL authorization with a restricted user
    Authenticate as a low-privileged user and query the GraphQL endpoint for sensitive data (e.g., hosts, organizations, or settings the user should not have permission to view). Compare results to what the REST API returns for the same user
    Affected if GraphQL returns more data, different records, or metadata that the REST API filters out for the same user account
  5. Compare GraphQL vs REST API responses for same user
    As the restricted user, make equivalent requests to both /api/v2/hosts (REST) and a GraphQL host query, then diff the results
    Affected if GraphQL response contains resources, fields, or associations that the REST API properly excludes based on user permissions

Your environment is affected if you run a vulnerable Foreman/Satellite version AND the GraphQL API is accessible to low-privileged users who can retrieve unauthorized data not filtered by their assigned permissions.

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
Upgrade available Upgrade to 3.16.2 or later
Fixed in 3.16.2
Interim mitigation

Apply proper permission filtering to all GraphQL queries and mutations to match REST API authorization behavior. Until a patch is available, consider restricting or disabling GraphQL API access for low-privileged users.

Fix this in Satellite Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
27.0 hours of engineering $4,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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