# CVE-2026-1031: Cross-site scripting in Common Licensing

> An unauthenticated attacker can inject JavaScript into the IBM License Key Server web interface to steal credentials from trusted sessions.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 18 Sep 2026
- **Updated:** 19 Sep 2026
- **Also known as:** GHSA-m729-455r-m59h

## What is CVE-2026-1031?

CVE-2026-1031 is a medium-severity cross-site scripting vulnerability in IBM Common Licensing, published on 18 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

IBM Common Licensing Agent 9.0, Agent 9.0.0.1, Agent 9.0.0.2, ART 9.0, ART 9.0.0.1, and ART 9.0.0.2 is vulnerable to cross-site scripting. This vulnerability allows an unauthenticated attacker to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted session.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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


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

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

## Is CVE-2026-1031 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-1031 is a medium-severity cross-site scripting vulnerability in IBM Common Licensing, published on 18 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-1031 in the wild and no public exploit code.

Affected product: IBM Common Licensing. 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-1031/ (Markdown: https://insights.sbomify.com/CVE-2026-1031/index.md)
```

## Sources

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

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