CVE-2026-27941
Openlit Software Development Kit 1.36.2 – 1.37.1
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:HSummary
CVE-2026-27941 is a critical-severity Inclusion of Functionality from Untrusted Control Sphere (CWE-829) vulnerability in Openlit Openlit Software Development Kit. Its CVSS base score is 9.9 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Supply Chain Compromise (T1195); ranked at the 33th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
This vulnerability is AI-related — categorised as LLM Application Platforms; in the Supply Chain and Deployment risk domain.
The strongest mitigations our analysis identified map to SR-4 (Provenance) and SR-11 (Component Authenticity) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-27941 is a high-severity vulnerability (CVSS 9.9, CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H) affecting GitHub Actions workflows in the OpenLIT open-source platform for AI engineering. Prior to version 1.37.1, several workflows in the OpenLIT GitHub repository improperly used the `pull_request_target` event trigger. This allowed the workflows to check out and execute untrusted code from pull requests originating from forked repositories, while running in the elevated security context of the base repository. The context included a write-privileged `GITHUB_TOKEN` and exposure to sensitive secrets such as API keys, database and vector store tokens, and a Google Cloud service account key. The issue stems from CWE-829 (Inclusion of Functionality from Untrusted Control Sphere).
An attacker with low privileges (PR:L), such as a user able to fork the repository and submit a pull request, can exploit this vulnerability remotely over the network with no user interaction required. By crafting a malicious pull request containing arbitrary code in the workflow, the attacker triggers execution in the base repository's privileged context. This grants full read/write access to the repository via the `GITHUB_TOKEN`, as well as exfiltration or misuse of all exposed secrets, potentially leading to compromise of linked services like databases, vector stores, and Google Cloud resources. The changed scope (S:C) amplifies impact across confidentiality, integrity, and availability.
The vulnerability was addressed in OpenLIT version 1.37.1, which contains a fix detailed in commit 4a62039a1659d6cbb8913172693f587b5fc2546c. Security practitioners should upgrade to this version or later and review workflows for similar misuse of `pull_request_target`. Additional guidance is available in the GitHub Security Advisory at GHSA-9jgv-x8cq-296q.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-8804
Vulnerability Data
OpenLIT is an open source platform for AI engineering. Prior to version 1.37.1, several GitHub Actions workflows in OpenLIT's GitHub repository use the `pull_request_target` event while checking out and executing untrusted code from forked pull requests. These workflows run with…
more
the security context of the base repository, including a write-privileged `GITHUB_TOKEN` and numerous sensitive secrets (API keys, database/vector store tokens, and a Google Cloud service account key). Version 1.37.1 contains a fix.
- CWE(s)
AI Security AnalysisAI
- AI Category
- LLM Application Platforms
- Risk Domain
- Supply Chain and Deployment
- OWASP Top 10 for LLMs 2025
- None mapped
- Classification Reason
- Matched keywords: ai
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 6 hardening rules · 6 OS baselines
V14.2.3V3.5.6V9.1.3V15.3.2
Mitigating Controls (NIST 800-53 r5) AI
Requires documented, valid provenance for components, preventing acceptance of code from outside the trusted sphere.
Implements detection and prevention of counterfeit or inauthentic components before they are integrated.
Establishes processes to identify and address supply-chain weaknesses that would allow untrusted functionality.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Pre-acquisition integrity/authenticity checks directly prevent inclusion of untrusted code.
Supply-chain program directly governs inclusion of third-party executable code.
Contractual requirements can mandate trusted sources and integrity checks for included functionality.
Supplier risk assessment explicitly covers risks from their products and libraries.
Critical-supplier assessment reduces risk of importing executable functionality from untrusted parties.
Secure SDLC practices include dependency vetting and trusted-source policies.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
By requiring suppliers to propagate security requirements and to disclose component provenance, the control limits the inclusion of functionality obtained from untrusted third-party sources without oversight.
Blocking domains that serve malware or untrusted scripts prevents the browser from automatically including functionality from an attacker-controlled source.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).
Oracle Linux 8 (1 rule)
- V-248635 Executable search paths within the initialization files of all local interactive OL 8 users must only contain paths that resolve to the system default or the user's home directory. prevents CWE-829
Oracle Linux 9 (1 rule)
- V-271847 OL 9 must be configured so that executable search paths within the initialization files of all local interactive users must only contain paths that resolve to the system default or the users home directory. prevents CWE-829
RHEL 7 (1 rule)
- V-204477 The Red Hat Enterprise Linux operating system must be configured so that all local interactive user initialization files executable search paths contain only paths that resolve to the users home directory. prevents CWE-829
RHEL 8 (1 rule)
- V-230317 Executable search paths within the initialization files of all local interactive RHEL 8 users must only contain paths that resolve to the system default or the users home directory. prevents CWE-829
RHEL 9 (1 rule)
- V-258050 Executable search paths within the initialization files of all local interactive RHEL 9 users must only contain paths that resolve to the system default or the users home directory. prevents CWE-829
Windows 10 (1 rule)
- V-220737 Administrative accounts must not be used with applications that access the Internet, such as web browsers, or with potential Internet sources, such as email. prevents CWE-829