# CVE-2026-44188: Auth bypass in Red Hat Ansible Automation Platform 2

> Attackers can hijack sessions by reusing stolen OAuth tokens that are not invalidated upon logout, gaining unauthorized read access to Ansible resources.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A: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:** 15 Jun 2026
- **Updated:** 20 Aug 2026
- **Also known as:** GHSA-r7cm-w9ch-cf3g, UBUNTU-CVE-2026-44188

## What is CVE-2026-44188?

CVE-2026-44188 is a medium-severity authentication bypass vulnerability in Red Hat Ansible Automation Platform 2, published on 15 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A flaw was found in Ansible Lightspeed. This vulnerability, related to insufficient session expiration, allows a remote attacker to maintain persistent access to the Ansible Lightspeed instance. If an attacker exfiltrates a valid OAuth (Open Authorization) access token before a user logs out, they can continue to authenticate and access sensitive data. This is because the application fails to invalidate the token on the backend, leaving it valid until its natural expiration. This can lead to unauthorized read access to Ansible resources such as inventories, playbooks, and configuration data.

Weakness: CWE-613 (DEPRECATED: Insufficient Session Expiration)

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


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

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

## Is CVE-2026-44188 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-44188 is a medium-severity authentication bypass vulnerability in Red Hat Ansible Automation Platform 2, published on 15 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-44188 in the wild and no public exploit code.

Affected product: Red Hat Ansible Automation Platform 2. 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-44188/ (Markdown: https://insights.sbomify.com/CVE-2026-44188/index.md)
```

## Sources

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

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