# CVE-2026-103094: Cleartext Storage of OAuth Credentials in ServiceNow AI Platform


- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:H/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 29 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-22w9-gfhr-4v85

## What is CVE-2026-103094?

CVE-2026-103094 is a high-severity vulnerability in ServiceNow AI Platform, published on 29 Oct 2026. 

### Official description

ServiceNow has remediated an information disclosure vulnerability that was identified in the ServiceNow AI Platform. This vulnerability could cause a user's plaintext password to be persisted in a system table, potentially exposing that password to a user who otherwise would not be entitled to view it.

ServiceNow remediated the vulnerability through security updates that address the unintended persistence of plaintext credentials. We are not currently aware of malicious exploitation against ServiceNow instances. We recommend customers promptly apply appropriate updates or upgrade to a patched release if they have not already done so.

Weakness: CWE-256 (Plaintext Storage of a Password)

## Which versions are affected by CVE-2026-103094?


## How do I fix CVE-2026-103094?

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

## Is CVE-2026-103094 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-103094 and fix it if it is affected.

What it is: CVE-2026-103094 is a high-severity vulnerability in ServiceNow AI Platform, published on 29 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-103094 in the wild and no public exploit code.

Affected product: ServiceNow AI 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-2026-103094/ (Markdown: https://insights.sbomify.com/CVE-2026-103094/index.md)
```

## Sources

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

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