# CVE-2025-2157: Foreman: disclosure of executed commands and outputs in foreman / red hat satellite

> Low-privileged users can access temporary files containing sensitive command outputs, leading to information disclosure and potential privilege escalation.

- **Severity:** Low 3.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Mar 2025
- **Updated:** 21 Nov 2025
- **Also known as:** GHSA-f324-3fxj-hh78

## What is CVE-2025-2157?

CVE-2025-2157 is a low-severity vulnerability in Red Hat Satellite 6, published on 15 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A flaw was found in Foreman/Red Hat Satellite. Improper file permissions allow low-privileged OS users to monitor and access temporary files under /var/tmp, exposing sensitive command outputs, such as /etc/shadow. This issue can lead to information disclosure and privilege escalation if exploited effectively.

Weakness: CWE-922 (Insecure Storage of Sensitive Information)

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


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

No fix has been published for CVE-2025-2157 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-2157 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-2157 is a low-severity vulnerability in Red Hat Satellite 6, published on 15 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-2157 in the wild and no public exploit code.

Affected product: Red Hat Satellite 6. No package-level version data is available, so check the vendor advisory linked from the reference page.

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

## Sources

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

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