p PatchFirst

CVE-2026-44188

CVE-2026-44188 · Ansible-lightspeed: ansible lightspeed: session hijacking and unauthorized data access due to insufficient session expiration

This page contains facts from public vulnerability sources. Check the original advisory before updating.

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.

CVSS 5.3 · Medium · EPSS 0.3%

Published
Updated

Stack: system

Affected products and versions

  • red hat ansible automation platform 2.6

    Versions
    • ≥ 1782755166: Not affected (rpm)

    No fix published

  • red hat ansible automation platform 2.7

    Versions
    • ≥ 1781025813: Not affected (rpm)

    No fix published

  • red hat ansible automation platform 2

    No fix published

  • ansible Ubuntu:Pro:14.04:LTS

    Versions
    • 1.1+dfsg-1
    • 1.3.4+dfsg-1
    • 1.4.0+dfsg-1
    • 1.4.1+dfsg-1
    • 1.4.3+dfsg-1
    • 1.4.4+dfsg-1
    • 1.5.4+dfsg-1
    • 1.5.4+dfsg-1ubuntu0.1~esm1
    • 1.5.4+dfsg-1ubuntu0.1~esm2
    • 1.5.4+dfsg-1ubuntu0.1~esm3
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • ansible Ubuntu:Pro:16.04:LTS

    Versions
    • 1.9.2+dfsg-2
    • 1.9.4-1
    • 2.0.0.2-2
    • 2.0.0.2-2ubuntu1
    • 2.0.0.2-2ubuntu1.1
    • 2.0.0.2-2ubuntu1.2
    • 2.0.0.2-2ubuntu1.3
    • 2.0.0.2-2ubuntu1.3+esm1
    • 2.0.0.2-2ubuntu1.3+esm2
    • 2.0.0.2-2ubuntu1.3+esm3
    • 2.0.0.2-2ubuntu1.3+esm4
    • 2.0.0.2-2ubuntu1.3+esm5
    • 2.0.0.2-2ubuntu1.3+esm6
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • lightspeed Ubuntu:16.04:LTS

    Versions
    • 1.2a-10
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • ansible Ubuntu:Pro:18.04:LTS

    Versions
    • 2.3.1.0+dfsg-2
    • 2.5.0+dfsg-1
    • 2.5.1+dfsg-1
    • 2.5.1+dfsg-1ubuntu0.1
    • 2.5.1+dfsg-1ubuntu0.1+esm1
    • 2.5.1+dfsg-1ubuntu0.1+esm2
    • 2.5.1+dfsg-1ubuntu0.1+esm3
    • 2.5.1+dfsg-1ubuntu0.1+esm4
    • 2.5.1+dfsg-1ubuntu0.1+esm5
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • lightspeed Ubuntu:18.04:LTS

    Versions
    • 1.2a-10build1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • ansible Ubuntu:Pro:20.04:LTS

    Versions
    • 2.8.3+dfsg-1
    • 2.8.6+dfsg-1
    • 2.9.2+dfsg-1
    • 2.9.4+dfsg-1
    • 2.9.6+dfsg-1
    • 2.9.6+dfsg-1ubuntu0.1~esm1
    • 2.9.6+dfsg-1ubuntu0.1~esm2
    • 2.9.6+dfsg-1ubuntu0.1~esm3
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • lightspeed Ubuntu:20.04:LTS

    Versions
    • 1.2a.debian.1-2
    • 1.2a.debian.1-2build1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • ansible-core Ubuntu:22.04:LTS

    Versions
    • 2.12.0-1
    • 2.12.0-1ubuntu0.1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • lightspeed Ubuntu:22.04:LTS

    Versions
    • 1.2a.debian.1-3
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • ansible Ubuntu:Pro:22.04:LTS

    Versions
    • 2.10.7+merged+base+2.10.8+dfsg-1
    • 2.10.7+merged+base+2.10.8+dfsg-1ubuntu0.1~esm1
    • 2.10.7+merged+base+2.10.8+dfsg-1ubuntu0.1~esm4
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • ansible Ubuntu:24.04:LTS

    Versions
    • 7.7.0+dfsg-1
    • 7.7.0+dfsg-3
    • 9.2.0+dfsg-0ubuntu4
    • 9.2.0+dfsg-0ubuntu5
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • ansible-core Ubuntu:24.04:LTS

    Versions
    • 2.14.9-2
    • 2.14.11-1
    • 2.14.11-2
    • 2.14.13-1
    • 2.16.3-0ubuntu1
    • 2.16.3-0ubuntu2
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • ansible Ubuntu:25.10

    Versions
    • 11.2.0+dfsg-1
    • 12.0.0~a2+dfsg-1
    • 12.0.0~a4+dfsg-1
    • 12.0.0~a6+dfsg-1
    • 12.0.0~b1+dfsg-1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • ansible-core Ubuntu:25.10

    Versions
    • 2.18.1-4ubuntu1
    • 2.19.0~beta4-1ubuntu1
    • 2.19.0-1ubuntu1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • ansible Ubuntu:26.10

    Versions
    • 13.1.0+dfsg-1ubuntu1
    • 13.4.0+dfsg-1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • ansible-core Ubuntu:26.10

    Versions
    • 2.20.1-1
    • 2.21.1~rc1-1
    • 2.21.1~rc1-2
    • 2.21.1~rc1-2ubuntu1
    • 2.22.0~beta2-1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • ansible Ubuntu:26.04:LTS

    Versions
    • 12.0.0~b1+dfsg-1
    • 12.0.0+dfsg-1
    • 12.2.0+dfsg-1
    • 13.1.0+dfsg-1
    • 13.1.0+dfsg-1ubuntu1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • ansible-core Ubuntu:26.04:LTS

    Versions
    • 2.19.0-1ubuntu1
    • 2.19.4-1
    • 2.20.1-1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

Original sources

Check your server →