PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-24138 FOGProject CVE debrief

CVE-2026-24138 is an unauthenticated SSRF vulnerability in FOG, a free open-source cloning/imaging/rescue suite/inventory management system. The vulnerability affects versions 1.5.10.1754 and below, and can be triggered by providing a user-controlled URL parameter in getversion.php. This issue appears to be reachable without an authenticated web session when the request includes newService=1. The vulnerability can be used to fetch both internal websites and files on the machine running FOG.

Vendor
FOGProject
Product
Unknown
CVSS
HIGH 7.5
CISA KEV
Not listed in stored evidence
Original CVE published
2026-01-23
Original CVE updated
2026-10-06
Advisory published
2026-01-23
Advisory updated
2026-10-06

Who should care

Defenders responsible for FOG installations, particularly those using versions 1.5.10.1754 and below, should assess exposure and potential impact. This includes operators, platform administrators, vulnerability management teams, and security teams who need to verify exposure, assess potential impact, and implement compensating controls to limit access to internal resources.

Why it matters

CVE-2026-24138 is an unauthenticated SSRF vulnerability in FOG that can be used to access internal resources. Defenders should prioritize verifying exposure and assessing potential impact.

  • Potential access to internal resources
  • Possible data leakage or unauthorized access

Technical summary

The vulnerability is caused by an unauthenticated SSRF issue in getversion.php, which can be triggered by providing a user-controlled URL parameter. This issue appears to be reachable without an authenticated web session when the request includes newService=1. The vulnerability can be used to fetch both internal websites and files on the machine running FOG, potentially allowing access to sensitive information or disrupting service. Defenders should prioritize verifying exposure and assessing potential impact, as the vulnerability can be used to access internal resources.

Defensive priority

Defenders should prioritize verifying exposure and assessing potential impact, as the vulnerability can be used to access internal resources.

Recommended defensive actions

  • Verify exposure by checking FOG version and configuration
  • Assess potential impact by identifying internal resources that could be accessed
  • Implement compensating controls to limit access to internal resources
  • Review relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
  • Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed

Evidence notes

The vulnerability is described in the CVE record and NVD vulnerability detail page. The source reference provides additional information on the vulnerability. Evidence limits suggest that defenders verify FOG version and configuration to assess exposure. The unauthenticated SSRF issue in getversion.php can be triggered by providing a user-controlled URL parameter, potentially allowing access to internal websites and files.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-24138 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-24138

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-24138 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-24138

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.