# CVE-2026-19543: Missing authorization in Common Licensing

> Attackers can bypass client-side validation by modifying requests to submit unauthorized values, leading to unintended application behavior in IBM License Key Server tools.

- **Severity:** Medium 6.2 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Sep 2026
- **Updated:** 14 Sep 2026
- **Also known as:** GHSA-7q7r-rggc-8hm5

## What is CVE-2026-19543?

CVE-2026-19543 is a medium-severity missing authorization vulnerability in IBM Common Licensing, published on 14 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### 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 performs input validation exclusively on the client side and fails to enforce the same restrictions on the server side. An attacker can modify requests to bypass validation controls and submit unauthorized values, potentially resulting in unintended application behavior.

Weakness: CWE-20 (Improper Input Validation)

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


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

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

## Is CVE-2026-19543 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-19543 is a medium-severity missing authorization vulnerability in IBM Common Licensing, published on 14 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-19543 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-19543/ (Markdown: https://insights.sbomify.com/CVE-2026-19543/index.md)
```

## Sources

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

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