Before commit 8eb3567, a workflow in the pgai repository could be abused to exfiltrate all secrets available to that workflow. Exposed secrets included a write-capable GITHUB_TOKEN, enabling an attacker to modify repository contents, push arbitrary code, and create releases.
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.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This is a 100-file automated research snapshot of Timescale pgai, explicitly described as a lab artifact for reproducing published GitHub Actions workflow vulnerabilities rather than an upstream-targeting exploit. It is primarily a pgai monorepo snapshot containing GitHub Actions workflows, documentation, SQL/Python/Docker examples, a Discord RAG bot, FastAPI demos, embedding evaluations, and extension development material. No dedicated exploit launcher or reverse-shell payload is present. The actionable issue is in `.github/workflows/ci.yml`: jobs triggered by `pull_request_target` check out the external PR head ref/SHA and execute attacker-modifiable Docker build inputs and `just` recipes. The same jobs pass model-provider secrets into later `docker exec` test commands. Consequently, an approved malicious fork PR can run arbitrary code in CI and access those secrets. The README states that this snapshot uses dummy values and that upstream Timescale is not the intended target.
3 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.