Secuno
ENNL
Book demo

CVE-2026-81268

8.1 HIGHEPSS 0.31%
  1. Published10 Sept 2026

Description

IBM Langflow OSS 1.0.0 through 1.11.5 could allow a remote authenticated attacker to execute flows and obtain sensitive information due to insufficient session expiration of API keys after user deactivation.

CVSS 3.1 breakdown

Attack vectorNetwork
Attack complexityLow
Privileges requiredLow
User interactionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityNone
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Affected products

Langflow Langflow≥ 1.0.0 < 1.11.6

Remediation

Fixed in
Langflow Langflow≥ 1.11.6

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

CVE-2026-864629.1
Apache Airflow FAB provider: changing a user's password through the Admin user-edit…
CVE-2026-823119.8
Apache Airflow FAB provider: resetting a user's password does not delete that user's…
CVE-2026-844809.8
WWBN AVideo fails to validate password recovery token expiration in…
CVE-2026-842038.1
Memos versions 0.26.0 through 0.30.0 fail to revoke refresh tokens when a user changes…
CVE-2026-149509.8
An unauthenticated remote attacker in possession of a valid session identifier is able…
CVE-2026-600539.1
Insufficient Session Expiration vulnerability in Apache Answer. This issue affects…

Frequently asked

Is CVE-2026-81268 being actively exploited?

CVE-2026-81268 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.31%.

How severe is CVE-2026-81268?

CVE-2026-81268 has a CVSS 3.1 base score of 8.1, rated high. EPSS estimates a 0.31% probability of exploitation.

Which products are affected by CVE-2026-81268?

Affected products include Langflow Langflow.

How do I fix CVE-2026-81268?

Upgrade affected software to a fixed version, for example Langflow Langflow 1.11.6 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-81268 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation worksBook a demo

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.