Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-39117 – Unauthenticated SSRF Leading to Cloud Credential Theft – AltumCode 66Uptime < 54.0.

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-39117 is a critical unauthenticated Server-Side Request Forgery (SSRF) vulnerability in AltumCode’s 66Uptime uptime/cronjob monitoring application, specifically in its ping-servers plugin. The flaw allows a remote, unauthenticated attacker to force the application server to issue arbitrary outbound HTTP requests, which can be leveraged to steal cloud instance credentials, scan internal networks, and pivot to internal services. The issue carries a CVSS v3.1 base score of 9.8 (Critical) and affects 66Uptime before version 54.0.0 and the ping-servers plugin before version 2.0.0.

Technical details

  • Root cause: The ping server endpoint (ping-server/index.php) processes user-supplied target parameters (check type, target URL, timeout) without authentication or input validation before the server performs the outbound network request.
  • Trigger conditions: No authentication or prior session is required — a single unauthenticated HTTP POST request to a discovered ping server endpoint is sufficient to trigger the request forgery.
  • Attack vector: Network-based (AV:N), low complexity, no privileges or user interaction required.
  • Impact: By pointing the target parameter at the cloud instance metadata service (e.g., 169.254.169.254/latest/meta-data/iam/security-credentials/), an attacker can retrieve live IAM/cloud credentials. The same primitive can be used for internal network enumeration, TCP port scanning, access to internal APIs/databases, and denial-of-service amplification against third-party hosts. The public CVE record classifies the underlying weakness as improper control of code generation (CWE-94) and describes the impact as remote code execution via index.php, reflecting the severity of what can ultimately be achieved (e.g., credential theft enabling further compromise) once the request-forgery primitive is exploited.

Affected software

  • AltumCode 66Uptime — versions before 54.0.0
  • 66Uptime ping-servers plugin — versions before 2.0.0

Severity

  • CVSS v3.1 Base Score: 9.8 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: Upgrade 66Uptime to version 54.0.0 or later, and the ping-servers plugin to version 2.0.0 or later.
  • Important post-patch step: The patched versions introduce an optional API key for authenticating ping-server requests, but this key is empty by default. Installations that upgrade without explicitly configuring the API key remain exploitable. Administrators must manually set and enforce an API key after upgrading.
  • Additional network mitigations: Restrict or firewall access to the ping-servers plugin endpoint to trusted networks only, disable cloud instance metadata access (e.g., enforce IMDSv2 or block link-local metadata addresses at the network/hypervisor level) for hosts running 66Uptime, and monitor for outbound requests from the application host to internal or link-local IP ranges.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge