Advisory record · GHSA-9jgv-x8cq-296q

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 ou...

CVSS 10.0 CriticalCriticalEPSS 0.0045 · 39th percentile

Critical, because:

  • CVSS score 10.0: 9.0 or more.

How we decide what’s critical

Published by the GitHub Advisory Database at 26 Feb 2026, 02:16 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
openlitPyPI>=1.36.2, <1.37.11.37.1
Identifiers
GHSA-9jgv-x8cq-296q · CVE-2026-27941 · PYSEC-2026-2246
Weakness (CWE)
CWE-829
Published
26 Feb 2026
Updated
13 Jul 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Versions of openlit from 1.36.2 up to but not including 1.37.1 are affected, due to GitHub Actions workflows in the project's repository that run untrusted code from forked pull requests with base-repository privileges. An attacker who can open a pull request from a fork could run code with a write-privileged token and access to sensitive repository secrets, such as API keys and a Google Cloud service account key. Upgrade openlit to version 1.37.1 or later.

Written 6 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
10.0 Critical 3.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0045, the 39th percentile, on 7 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 15:04 UTC First seen by agentprime
  2. 31 Oct 2026, 15:04 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.