dbcve.org
SatelliteApplication · Redhat

CVE-2026-5142

MEDIUM · 6.5 CVSS v3.1 Published 2026-07-01
Fix available
A fix is available. Upgrade to 3.18.2 / 3.19.1 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click 7 weeks old

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 foreman. Authenticated users with 'view_keypairs' permission can bypass taxonomy scoping, allowing them to download private SSH (Secure Shell) keys from other organizations by directly querying key pair IDs. This vulnerability leads to cross-tenant data exposure in multi-tenant deployments, potentially compromising sensitive information.

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

In Foreman, authenticated users with 'view_keypairs' permission can bypass taxonomy organization boundaries by directly querying keypair IDs, allowing them to download private SSH keys from other organizations. This is a cross-tenant authorization bypass where taxonomy scoping is not enforced on keypair access.

MitigationImplement mandatory taxonomy validation in the keypair controller to ensure users can only access keypairs within their organization, and consider adding audit logging for keypair access to detect unauthorized cross-tenant queries.

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.18, < 6.18.7>= 6.16, < 6.16.10>= 6.17, < 6.17.9>= 6.19, < 6.19.2
ForemanApplication
Affected:< 3.18.2>= 3.19.0, < 3.19.1

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 installed Foreman version
    Run 'foreman --version' or check /usr/share/foreman/.version file to determine the exact version installed
    Affected if Version is < 3.18.2 or >= 3.19.0 and < 3.19.1 (for Theforeman Foreman)
  2. Check installed Red Hat Satellite version
    Run 'satellite-installer --version' or check /etc/redhat-release to determine the Satellite version
    Affected if Version is >= 6.18 and < 6.18.7, or >= 6.16 and < 6.16.10, or >= 6.17 and < 6.17.9, or >= 6.19 and < 6.19.2
  3. Verify keypair feature is in use
    Query the API endpoint /api/keypairs to list accessible keypairs, or check database tables key_pairs or keypairs for existing entries
    Affected if Keypairs exist in the system and are accessible to authenticated users with view_keypairs permission
  4. Check taxonomy organization enforcement on keypair access
    Using an API token with view_keypairs permission, attempt to query a keypair from a different organization by its ID (e.g., GET /api/keypairs/<id>), and verify whether the response returns the private key or returns a 404/403 error
    Affected if The API returns private key details for keypairs outside the user's organization, indicating taxonomy boundaries are not enforced

If the installed version falls within any affected range AND keypairs exist in the system AND cross-organization keypair queries succeed without proper authorization checks, the environment is vulnerable to CVE-2026-5142.

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.

dbcve · scoped
Upgrade available Upgrade to 3.18.2 / 3.19.1 / 6.16.10 or later
Fixed in 3.18.23.19.16.16.10
Interim mitigation

Implement mandatory taxonomy validation in the keypair controller to ensure users can only access keypairs within their organization, and consider adding audit logging for keypair access to detect unauthorized cross-tenant queries.

Recommended fix High confidence

Foreman: 3.18.2 or 3.19.1 | Satellite: 6.18.7, 6.16.10, 6.17.9, or 6.19.2 (depending on current branch)

  1. 1. Identify the currently installed Foreman or Satellite version using 'foreman-installer --version' or 'satellite-installer --version'
  2. 2. Back up all Foreman/Satellite data, including the database and configuration files, before proceeding with the upgrade
  3. 3. For Foreman: If running < 3.18.2, upgrade to version 3.18.2; if running >= 3.19.0 and < 3.19.1, upgrade to version 3.19.1
  4. 4. For Satellite: If running >= 6.18 and < 6.18.7, upgrade to version 6.18.7; if running >= 6.16 and < 6.16.10, upgrade to version 6.16.10; if running >= 6.17 and < 6.17.9, upgrade to version 6.17.9; if running >= 6.19 and < 6.19.2, upgrade to version 6.19.2
  5. 5. Follow the standard upgrade procedure documented in the Foreman or Red Hat Satellite administration guides
  6. 6. After upgrade, verify that the 'view_keypairs' permission no longer allows cross-organization access to SSH keys
  7. 7. Confirm the fix by checking that taxonomy scoping is properly enforced for key pair resources
Caveat Standard upgrade risks apply - review release notes for your specific version for any configuration or API changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Satellite Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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