Foreman: seven vulnerabilities incl. code execution (CVE-2026-96658, CVE-2026-96659) fixed in 3.19.2 and 5.0.1
CVE-2026-12423 CVE-2026-12540 CVE-2026-12541 CVE-2026-12542 CVE-2026-12544 CVE-2026-96658 CVE-2026-96659
Published 13/11/2026 12:04
Timeline
2 events over 52 min
- 13/11/2026 11:12ConfirmedBSI CERT-Bund (WID)+52 min
- 13/11/2026 12:04Published on WatchtowerPro CISO
In short
The Foreman project's advisory list says seven CVEs are fixed in Foreman 3.19.2 and 5.0.1. The most serious, CVE-2026-96658, lets a low-privileged user who can render template content reach Ruby code execution as the Foreman service, with a vendor score of CVSS 9.9 (Critical). Red Hat's Satellite 6.16.14 update lists CVE-2026-96658 and CVE-2026-96659 as fixed. Shodan recognises at least 80 internet-facing Foreman servers worldwide, 6 of them in the EU (17/11/2026); the real number is likely higher, and how many run an affected version is not yet known.
How bad is it
Critical. A logged-in user with only low privileges who can render templates can run their own code on the Foreman server, and a Viewer can read secrets such as host root passwords.
Confirmed by the vendor or a CERT - no exploitation reported yet.
Severity score
The worst of 7 CVEs · CVSS 3.1 from NVD, from redhat.com, read 16/11/2026.
What an attacker needs
- Internet access to itEnough
- A loginA user account
- A user to clickNo
- Special settingsNo
Red helps the attacker, blue holds them back, grey is not published yet.
If it works, an attacker can
- Run their own code on the system
- Read the data it holds
- Change some of its data
- Slow it down or interrupt it
Type: code execution.
A score is the worst case for the flaw, not a verdict on any one system. How we score · ReconX customers see which of their own systems are affected.
Affected versions
- CVE-2026-96658 (Safemode bypass leading to code execution): Foreman releases bundling Safemode before 2.0.1, including 3.19.0, 3.19.1 and 5.0.0.
- CVE-2026-96659 (Viewer role reads data through template preview): Foreman 1.9.0 to 3.19.1, and 5.0.0.
- CVE-2026-12423 (unauthenticated request reaches build-host provisioning data): Foreman 1.1 to 3.19.1, and 5.0.0.
- CVE-2026-12540 (command injection in foreman-rake errors:fetch_log): Foreman 2.2.0 to 3.19.1, and 5.0.0. CVE-2026-12541 (command injection in foreman-rake database tasks): 1.5.0 to 3.19.1, and 5.0.0.
- CVE-2026-12542 (command injection in foreman-tail, local user needed): Foreman 1.5.0 to 3.19.1, and 5.0.0. CVE-2026-12544 (template injection or unsafe deserialization at foreman-rake startup, needs control of configuration): 1.0 to 3.19.1, and 5.0.0.
Fixed in
- 3.19 branch: 3.19.2
- 5.0 branch: 5.0.1
What to do now
- Update to Foreman 3.19.2 (3.19 line) or Foreman 5.0.1 (5.0 line).
- Verify that Safemode 2.0.1 or later is installed (CVE-2026-96658).
- Red Hat Satellite 6.16 customers: install the Satellite 6.16.14 async update.
- Until updated, review and reduce template-render, template-preview and Viewer role holders, and keep Safemode enabled. These interim measures reduce exposure and do not make a server safe.
- Because template preview can expose host root passwords, consider rotating them if misuse is suspected.
ReconX customers see the full notice - and their own systems
Our customers are alerted at every phase. Until a patch exists, the ReconX agent watches their servers from the inside for anomalies, and our outside view - the attacker's view - shows which systems to fix first.
In ReconX: the full analysis, 4 open questions, followed up as sources answer and all 2 sources with their dates. And technology matching: which of your systems run Foreman, at which version, fixed or not - and what each one needs.
Main sources
[UPDATE] [kritisch] Foreman: Mehrere Schwachstellen CERT · RHSA-2026:12423 - Security Advisory Research