Loading vulnerability…
Prior to OpenLIT 1.37.1, multiple GitHub Actions workflows in the OpenLIT repository were configured to run on the pull_request_target event while checking out and executing code originating from forked pull requests. Because pull_request_target executes in the security context of the base repository, the workflow jobs ran with a write-privileged GITHUB_TOKEN and access to repository secrets (including API keys, database/vector store tokens, and a Google Cloud service account key). This unsafe combination allows untrusted PR code to execute with elevated CI privileges and access sensitive credentials. OpenLIT 1.37.1 fixes the affected workflows.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
GITHUB_TOKEN to modify repository contents and/or CI configuration. This can lead to compromise of the repository and downstream systems reachable via the exposed credentials.If you can’t patch tonight, do this now.
GITHUB_TOKEN permissions to least privilege (e.g., read-only) for PR contexts. Avoid using pull_request_target for jobs that check out PR code; prefer pull_request for untrusted contributions, or gate privileged steps behind maintainer-controlled conditions and avoid passing secrets to untrusted code paths.Patch, then assume compromise.
pull_request_target with access to secrets; restructure workflows to avoid secret exposure and remove unnecessary token permissions.No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
7 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.