# CVE-2026-19572: FlexNet Publisher lmadmin SOAP Authentication Bypass Vulnerability

> Unauthenticated attackers can bypass SOAP authentication to gain privileged administrator access in FlexNet Publisher lmadmin.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/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:** 7 Oct 2026
- **Updated:** 7 Oct 2026
- **Also known as:** GHSA-98jh-cm22-cgp2

## What is CVE-2026-19572?

CVE-2026-19572 is a critical authentication bypass vulnerability in Flexera FlexNet Publisher, published on 7 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A security vulnerability has been identified in FlexNet Publisher lmadmin. The vulnerability exists in a SOAP handler, where a hardcoded authentication bypass could allow an unauthenticated user to obtain a privileged administrator session without providing valid credentials.

Weakness: CWE-288 (Authentication Bypass Using an Alternate Path or Channel)

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


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

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

## Is CVE-2026-19572 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-19572 is a critical authentication bypass vulnerability in Flexera FlexNet Publisher, published on 7 Oct 2026. 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-2026-19572 in the wild and no public exploit code.

Affected product: Flexera FlexNet Publisher. 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-19572/ (Markdown: https://insights.sbomify.com/CVE-2026-19572/index.md)
```

## Sources

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

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