Security readout for executives and security teams
Plain-English summary
CVE-2026-27941 affects OpenLIT before 1.37.1. Certain GitHub Actions workflows could run untrusted pull request code with the main repository’s privileges and secrets. This creates a serious risk of source repository compromise and secret theft, especially for maintainers or forks using the same workflows.
Executive priority
Treat as urgent for teams maintaining OpenLIT repositories or using its workflows. The main business risk is compromise of development infrastructure and theft of cloud, database, or API secrets. Prioritize upgrade, workflow review, and credential rotation.
Technical view
The issue is misuse of GitHub Actions `pull_request_target` with checkout and execution of untrusted fork pull request code. Workflows ran in the base repository security context with a write-privileged `GITHUB_TOKEN` and multiple secrets. The advisory maps this to CWE-829 and rates it CVSS 10.0. Fixed in OpenLIT 1.37.1.
Likely exposure
Exposure is most relevant to the OpenLIT repository, maintainers, and organizations using affected OpenLIT versions or copied workflows before 1.37.1. Runtime deployments of OpenLIT are not clearly described as directly exploitable by the provided sources.
Exploitation context
A low-privileged attacker could abuse fork-based pull request automation if the vulnerable workflows are present. The provided sources do not state known active exploitation, and the CVE is not marked KEV in the supplied data.
Researcher notes
The vulnerability is supply-chain and CI/CD focused, not a typical application endpoint flaw. Evidence supports critical impact through secret exposure and repository write access. Avoid assuming downstream application RCE unless the affected GitHub Actions workflow context exists.
Mitigation direction
- Upgrade OpenLIT to version 1.37.1 or later.
- Review GitHub Actions workflows using `pull_request_target`.
- Avoid executing untrusted fork pull request code with repository secrets available.
- Rotate repository secrets that may have been exposed.
- Review GitHub token permissions for least privilege.
- Check the vendor advisory and fix commit for implementation details.
Validation and detection
- Confirm OpenLIT version is 1.37.1 or later.
- Inspect workflows for unsafe `pull_request_target` usage.
- Verify fork pull request workflows cannot access sensitive secrets.
- Review Actions history for suspicious pull request workflow runs.
- Confirm exposed API keys and cloud credentials were rotated.
- Validate repository token permissions are restricted.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-829: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupDatabase behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-27941 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 10 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H3.16Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
10CriticalVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/openlit/openlit/security/advisories/GHSA-9jgv-x8cq-296qCVE reference · x_refsource_CONFIRM
- https://github.com/openlit/openlit/commit/4a62039a1659d6cbb8913172693f587b5fc2546cCVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Inclusion of Functionality from Untrusted Control Sphere
Inclusion of Functionality from Untrusted Control Sphere represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.