# CVE-2025-3648: Data Inference in Now Platform via Conditional ACLs

> Attackers can infer unauthorized instance data via range queries under specific conditional ACL configurations in ServiceNow Now Platform.

- **Severity:** High 8.2 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Jul 2025
- **Updated:** 19 Aug 2025
- **Also known as:** GHSA-f77v-7fv6-253h

## What is CVE-2025-3648?

CVE-2025-3648 is a high-severity vulnerability in ServiceNow Now Platform, published on 8 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability has been identified in the Now Platform that could result in data being inferred without authorization. Under certain conditional access control list (ACL) configurations, this vulnerability could enable unauthenticated and authenticated users to use range query requests to infer instance data that is not intended to be accessible to them.

To assist customers in enhancing access controls, ServiceNow has introduced additional access control frameworks in Xanadu and Yokohama, such as Query ACLs, Security Data Filters and Deny-Unless ACLs.

Additionally, in May 2025, ServiceNow delivered to customers a security update that is designed to enhance customer ACL configurations.

Customers, please review the KB Articles in the References section.

Weakness: CWE-1220 (Insufficient Granularity of Access Control)

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


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

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

## Is CVE-2025-3648 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-3648 is a high-severity vulnerability in ServiceNow Now Platform, published on 8 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-3648 in the wild and no public exploit code.

Affected product: ServiceNow Now Platform. 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-3648/ (Markdown: https://insights.sbomify.com/CVE-2025-3648/index.md)
```

## Sources

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

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