CVE-2024-5178: Sensitive file read in ServiceNow SecurelyAccess API
CVE-2024-5178 is an incomplete input validation vulnerability in the SecurelyAccess API of ServiceNow Now Platform releases Washington DC, Vancouver, and Utah. Insufficient validation of file access requests allows an administrative user to bypass restrictions and read sensitive files on the web application server. The vulnerability is a post-authentication file disclosure issue; unauthenticated compromise requires chaining it with separate vulnerabilities.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
An attacker with administrative privileges can obtain sensitive server files that should remain inaccessible through the application. Disclosure can expose confidential configuration information and credentials, potentially supporting further compromise. Arbitrary code execution, full database access, and command execution on configured MID Servers are broader exploit-chain outcomes, not established standalone effects of this vulnerability.
Mitigation
If you can’t patch tonight, do this now.
No vulnerability-specific alternative workaround is documented. Apply the relevant security patches or hotfixes promptly. As defense-in-depth measures, restrict access to affected instances, enforce least privilege for administrative accounts, and increase access-log monitoring and suspicious-login detection. Investigate evidence of prior exploitation rather than treating patch installation as sufficient incident remediation.
Remediation
Patch, then assume compromise.
Install a vendor-designated fixed patch or hotfix for the affected release family. Utah: Patch 10 Hot Fix 3, Patch 10a Hot Fix 2, or Patch 10b Hot Fix 1. Vancouver: Patch 6 Hot Fix 2, Patch 7 Hot Fix 3b, Patch 8 Hot Fix 4, Patch 9 Hot Fix 1, or Patch 10. Washington DC: Patch 1 Hot Fix 3b, Patch 2 Hot Fix 2, Patch 3 Hot Fix 2, or Patch 4. Subsequent cumulative releases include these fixes. Patching prevents future exploitation but does not remediate an existing compromise.
Exploits
No public exploits tracked yet. Mallory keeps watching.
References
Frequently asked questions
- Is CVE-2024-5178 exploited in the wild?
- Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild.
- Is there a public exploit for CVE-2024-5178?
- As of Oct 16, 2026, Mallory has found no public exploit for CVE-2024-5178.
- Is there a patch for CVE-2024-5178?
- Install a vendor-designated fixed patch or hotfix for the affected release family. Utah: Patch 10 Hot Fix 3, Patch 10a Hot Fix 2, or Patch 10b Hot Fix 1.
- How severe is CVE-2024-5178?
- CVE-2024-5178 has a CVSS v4 score of 6.9 (Medium) and an EPSS score of 33.6% (98th percentile) as of Oct 16, 2026.
Recent activity
14 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.