# OpenChoreo: Unauthenticated build/workflow trigger via git-provider confusion (webhook signature bypass) Advisory record · `GHSA-c5f6-2rm9-2w8g` - **Identifiers:** `GHSA-c5f6-2rm9-2w8g` · `CVE-2026-73840` · `GO-2026-6360` - **State:** Confirmed - **Severity:** CVSS 5.3 Medium - **Critical:** No - **Weakness (CWE):** [CWE-287](https://cwe.mitre.org/data/definitions/287.html) · [CWE-290](https://cwe.mitre.org/data/definitions/290.html) · [CWE-345](https://cwe.mitre.org/data/definitions/345.html) - **Tags:** [Authentication bypass](https://agentprime.io/advisories/tag/auth-bypass.md) · [CWE-345](https://agentprime.io/advisories/tag/cwe-345.md) - **Published:** 2 Sept 2026 - **Updated:** 10 Sept 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 2 Sept 2026, 23:45 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Affected packages - `github.com/openchoreo/openchoreo` (Go): affected `<1.0.3 || >=1.1.0, <1.1.3 || >=1.2.0-rc.1, <1.2.0-rc.2`; fixed in `1.0.3`, `1.1.3`, `1.2.0-rc.2` ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > OpenChoreo versions before 1.0.3, from 1.1.0 before 1.1.3, and from 1.2.0-rc.1 before 1.2.0-rc.2 are affected. An unauthenticated attacker who can reach the autobuild webhook endpoint and knows a matching repository URL and branch can trigger builds of auto-build components, including ones configured for GitHub or GitLab, and in some setups cause unauthorized deployment. Upgrade to 1.0.3, 1.1.3, or 1.2.0-rc.2 or later. Written 1 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 - 5.3 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`, from CNA (GitHub_M) - **CISA KEV:** Not listed. - **EPSS:** 0.0035, the 28th percentile, on 6 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline - 31 Oct 2026, 14:13 UTC: First seen by agentprime - 31 Oct 2026, 14:13 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-c5f6-2rm9-2w8g) ## Sources - [GitHub Advisory Database: GHSA-c5f6-2rm9-2w8g](https://github.com/advisories/GHSA-c5f6-2rm9-2w8g) - [OSV: GHSA-c5f6-2rm9-2w8g](https://osv.dev/vulnerability/GHSA-c5f6-2rm9-2w8g) - - - - - - - - - - - - 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. ## Check whether this affects you A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet. - With the agentprime MCP server (), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .