CVE-2026-73840: OpenChoreo Unauthenticated Build/workflow Trigger Vulnerability

MODERATE
Advisory Identifier: GHSA-c5f6-2rm9-2w8g
CVSS 5.3
CWE-287 CWE-345 CWE-290
Published
Advisory Summary

CVE-2026-73840 is a MODERATE (CVSS 5.3) unauthenticated build/workflow trigger vulnerability (CWE-287: Improper Authentication) affecting OpenChoreo libraries in the Go ecosystem. The issue involves unauthenticated build/workflow trigger via git-provider confusion (webhook signature bypass). Remediation is available by upgrading affected packages to version 1.0.3, 1.1.3, 1.2.0-rc.2.

CVE-2026-73840 at a Glance

CVE Identifier CVE-2026-73840
GHSA Identifier GHSA-c5f6-2rm9-2w8g
Severity MODERATE
CVSS v3.1 Base Score 5.3
CWE Classification CWE-287: Improper Authentication
Affected Product OpenChoreo
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 5.3

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity None (I:N)
Availability Low (A:L)

How to Fix CVE-2026-73840

To remediate this vulnerability, upgrade all affected OpenChoreo dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/openchoreo/openchoreo fixed: 1.0.3
Upgrade github.com/openchoreo/openchoreo to 1.0.3
github.com/openchoreo/openchoreo fixed: 1.1.3
Upgrade github.com/openchoreo/openchoreo to 1.1.3
github.com/openchoreo/openchoreo fixed: 1.2.0-rc.2
Upgrade github.com/openchoreo/openchoreo to 1.2.0-rc.2
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/openchoreo/openchoreo

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-73840, inspect your project dependencies for OpenChoreo:

inspect dependencies for github.com/openchoreo/openchoreo

Analyze the terminal output to locate any version of OpenChoreo in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.0.3), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-287: Improper Authentication, where when an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. In OpenChoreo, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## Summary The OpenChoreo autobuild webhook endpoint (`POST /api/v1alpha1/autobuild`) selected the git provider used to authenticate an incoming webhook from a client-supplied request header rather than from the target component's configuration, and its Bitbucket provider accepted requests without a valid signature. A caller could set the `X-Event-Key` header to be treated as a Bitbucket webhook, bypassing the HMAC secret that otherwise protects GitHub and GitLab webhooks, and trigger a component build without authenticating. ## Impact An attacker who can reach the autobuild webhook endpoint and knows the repository URL and branch configured for an auto-build component can trigger a build for that component without authenticating — including components configured for GitHub or GitLab, since the provider used or verification is chosen by the caller rather than by the component's configuration. The triggered build runs against a commit SHA supplied by the attacker, and the component lookup is not scoped to a tenant or namespace, so any auto-build component across the cluster matching the given repository and branch is affected. This can result in unauthorized builds — and, where auto-deploy is configured, unauthorized deployment of attacker-influenced code — and can be used to exhaust build resources through repeated unauthenticated triggering. The exposure applies to any component with `spec.autoBuild: true`, regardless of which git provider it declares, wherever the autobuild webhook endpoint is network-reachable. ## Patches Fixed in 1.0.3, 1.1.3, and 1.2.0-rc.2. The fix validates Bitbucket webhooks with HMAC-SHA256 against the configured secret using the same verification path as GitHub, requires a configured, non-empty secret for every provider (a missing secret now rejects the request instead of skipping validation), and requires the authenticated provider to match the git provider configured for the matched component. Upgrading is non-disruptive — no component or webhook configuration changes are required beyond the standard upgrade. Upgrade path: 1.1.x → 1.1.3, 1.0.x and earlier → 1.0.3, 1.2 line → 1.2.0-rc.2 or later.

CVE-2026-73840 Affected OpenChoreo Versions

3 component(s)
Fixed Versions:
1.0.31.1.31.2.0-rc.2
Product / Package Ecosystem Affected Versions Fixed Version
github.com/openchoreo/openchoreo
Go
< 1.0.3
1.0.3
github.com/openchoreo/openchoreo
Go
≥ 1.1.0
< 1.1.3
1.1.3
github.com/openchoreo/openchoreo
Go
≥ 1.2.0-rc.1
< 1.2.0-rc.2
1.2.0-rc.2

References

Frequently Asked Questions

What is CVE-2026-73840?
CVE-2026-73840 is a security vulnerability in OpenChoreo involving Unauthenticated build/workflow trigger via git-provider confusion (webhook signature bypass) under CWE-287: Improper Authentication.
Which OpenChoreo versions are affected?
Affected versions include releases prior to 1.0.3, 1.1.3, 1.2.0-rc.2 across affected packages: github.com/openchoreo/openchoreo.
What version fixes CVE-2026-73840?
Upgrading to 1.0.3, 1.1.3, 1.2.0-rc.2 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/openchoreo/openchoreo affected?
Yes, github.com/openchoreo/openchoreo is affected in releases prior to 1.0.3, 1.1.3, 1.2.0-rc.2. Upgrade your dependency to 1.0.3, 1.1.3, 1.2.0-rc.2 or later.
What is the CVSS score of CVE-2026-73840?
CVE-2026-73840 has a CVSS v3.1 base score of 5.3 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L.
What CWE is associated with CVE-2026-73840?
CVE-2026-73840 is classified under CWE-287: Improper Authentication (When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.).
How can I check Go dependencies for CVE-2026-73840?
Run the dependency tree command: 'inspect dependencies for github.com/openchoreo/openchoreo'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-c5f6-2rm9-2w8g",
  "modified" : "2026-09-02T23:45:14Z",
  "published" : "2026-09-02T23:45:14Z",
  "aliases" : [ "CVE-2026-73840" ],
  "summary" : "OpenChoreo: Unauthenticated build/workflow trigger via git-provider confusion (webhook signature bypass)",
  "details" : "## Summary\nThe OpenChoreo autobuild webhook endpoint (`POST /api/v1alpha1/autobuild`) selected the git provider used to authenticate an incoming webhook from a client-supplied request header rather than from the target component's configuration, and its Bitbucket provider accepted requests without a valid signature. A caller could set the `X-Event-Key` header to be treated as a Bitbucket webhook, bypassing the HMAC secret that otherwise protects GitHub and GitLab webhooks, and trigger a component build without authenticating.\n\n## Impact\nAn attacker who can reach the autobuild webhook endpoint and knows the repository URL and branch configured for an auto-build component can trigger a build for that component without authenticating — including components configured for GitHub or GitLab, since the provider used or verification is chosen by the caller rather than by the component's configuration. The\ntriggered build runs against a commit SHA supplied by the attacker, and the component lookup is not scoped to a tenant or namespace, so any auto-build component across the cluster matching the given repository and branch is affected. This can result in unauthorized builds — and, where auto-deploy is configured, unauthorized deployment of attacker-influenced code — and can be used to exhaust build resources through repeated unauthenticated triggering.\n\nThe exposure applies to any component with `spec.autoBuild: true`, regardless of which git provider it declares, wherever the autobuild webhook endpoint is network-reachable.\n\n## Patches\nFixed in 1.0.3, 1.1.3, and 1.2.0-rc.2. The fix validates Bitbucket webhooks with HMAC-SHA256 against the configured secret using the same verification path as GitHub, requires a configured, non-empty secret for every provider (a missing secret now rejects the request instead of skipping validation), and requires the authenticated provider to match the git provider configured for the\nmatched component. Upgrading is non-disruptive — no component or webhook configuration changes are required beyond the standard upgrade. Upgrade path: 1.1.x → 1.1.3, 1.0.x and earlier → 1.0.3, 1.2 line → 1.2.0-rc.2 or later.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/openchoreo/openchoreo"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.0.3"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/openchoreo/openchoreo"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "1.1.0"
      }, {
        "fixed" : "1.1.3"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/openchoreo/openchoreo"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "1.2.0-rc.1"
      }, {
        "fixed" : "1.2.0-rc.2"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/openchoreo/openchoreo/security/advisories/GHSA-c5f6-2rm9-2w8g"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-73840"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/openchoreo/openchoreo/pull/4239"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/openchoreo/openchoreo/pull/4252"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/openchoreo/openchoreo/pull/4253"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/openchoreo/openchoreo/commit/268efd9b762a3f4f72b55d9c1b13dfc55122127b"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/openchoreo/openchoreo/commit/8af4a3fc8725fc2d8a9de9611e77278a5c48f978"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/openchoreo/openchoreo/commit/f540553db7143141b73bb37fae02102e6f082a34"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/openchoreo/openchoreo"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/openchoreo/openchoreo/releases/tag/v1.0.3"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/openchoreo/openchoreo/releases/tag/v1.1.3"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/openchoreo/openchoreo/releases/tag/v1.2.0-rc.2"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-287", "CWE-290", "CWE-345" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-09-02T23:45:14Z",
    "nvd_published_at" : "2026-08-13T22:17:28Z"
  }
}