# CVE-2025-0337: Authorization bypass in Now Platform

> An authenticated user can bypass authorization controls to access unauthorized data within the ServiceNow Now Platform.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Mar 2025
- **Updated:** 6 Mar 2025
- **Also known as:** GHSA-4x8m-chwm-9h7p

## What is CVE-2025-0337?

CVE-2025-0337 is a high-severity missing authorization vulnerability in ServiceNow Now Platform, published on 6 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

ServiceNow has addressed an authorization bypass vulnerability that was identified in the Washington release of the Now Platform. This vulnerability, if exploited, potentially could enable an authenticated user to access unauthorized data stored within the Now Platform that the user otherwise would not be entitled to access. 

This issue is addressed in the listed patches and family release, which have been made available to hosted and self-hosted customers, as well as partners.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2025-0337 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-0337 is a high-severity missing authorization vulnerability in ServiceNow Now Platform, published on 6 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-0337 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-0337/ (Markdown: https://insights.sbomify.com/CVE-2025-0337/index.md)
```

## Sources

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

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