Openlit Software Development KitApplication · Openlit
CVE-2026-27941
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedOpenLIT 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 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceOpenLIT's GitHub Actions workflows used the pull_request_target event to checkout and execute code from forked pull requests while running in the base repository's security context. This allowed attackers opening malicious pull requests to steal the write-privileged GITHUB_TOKEN and sensitive secrets (API keys, database/vector store tokens, Google Cloud service account key).
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Openlit Software Development KitApplication
>= 1.36.2, < 1.37.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed OpenLIT SDK versionRun 'pip show openlit' or check your package.json/requirements.txt for the openlit package versionAffected if Version is >=1.36.2 and <1.37.1
-
Locate GitHub Actions workflow filesCheck the .github/workflows/ directory in your OpenLIT repository for YAML workflow filesAffected if Workflow files exist and use pull_request_target trigger
-
Inspect workflow for pull_request_target with checkoutOpen each workflow YAML file and search for 'pull_request_target' combined with 'actions/checkout' actionAffected if Workflow uses pull_request_target trigger AND executes actions/checkout to process untrusted PR code
-
Verify workflow runs with elevated privilegesCheck if the workflow has write permissions on GITHUB_TOKEN or has access to secrets (GITHUB_TOKEN, custom secrets for API keys, cloud credentials)Affected if Workflow runs with elevated GITHUB_TOKEN permissions and has access to sensitive secrets
You are affected if you use OpenLIT SDK version >=1.36.2 and <1.37.1 and have GitHub Actions workflows using pull_request_target that checkout code from pull requests while having access to sensitive secrets.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.37.1
Upgrade to version 1.37.1 and audit all GitHub Actions workflows to ensure they do not use pull_request_target with checkout/execution of untrusted PR code, or implement proper permissions restrictions on GITHUB_TOKEN.
1.37.1
- Upgrade the OpenLIT SDK to version 1.37.1 or later using your package manager (e.g., `pip install openlit>=1.37.1` or `npm install openlit@latest`)
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Openlit Software Development Kit
Scoped from the published advisory
- Consultation6.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,048.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-27941 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-27941 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data