Allstar Reviewbot has Authentication Bypass via Hard-coded Webhook Secret

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

4.6 · CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:U · score source

EPSS

• CVE-2025-61926: 0.50% estimated exploitation activity in the next 30 days; percentile 43.04 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

A vulnerability in Allstar’s Reviewbot component caused inbound webhook requests to be validated against a hard-coded, shared secret: https://github.com/ossf/allstar/blob/294ae985cc2facd0918e8d820e4196021aa0b914/pkg/reviewbot/reviewbot.go#L59 The value used for the secret token was compiled into the Allstar binary and could not be configured at runtime. In practice, this meant that every deployment using Reviewbot would validate requests with the same secret unless the operator modified source code and rebuilt the component - an expectation that is not documented and is easy to miss. While Reviewbot is not commonly enabled in standard Allstar setups, we are issuing this advisory to reach any environments where it may have been deployed. Affected Versions All Allstar releases prior to v4.5 that include the Reviewbot code path are affected. Deployments on v4.5 and later are not affected. If you have not enabled or exposed the Reviewbot endpoint, this issue does not apply to your…

Published by the source

10 Oct 2025, 22:53 UTC

Last modified by the source

23 Oct 2025, 20:35 UTC

Source last checked

26 Oct 2026, 15:13 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-33f4-mjch-7fpr

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-61926

Advisory: Allstar Reviewbot has Authentication Bypass via Hard-coded Webhook Secret
IDs: CVE-2025-61926, GHSA-33f4-mjch-7fpr
Record: https://patchnext.com/advisories/cve-2025-61926 (revision 1, source checked 26 Oct 2026, 15:13 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.6)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/ossf/allstar 0.0.0-20250721181116-e004ecb540d6. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/ossf/allstar: affected < 0.0.0-20250721181116-e004ecb540d6; fixed in 0.0.0-20250721181116-e004ecb540d6

## Suggested inspection (read-only)
- Go github.com/ossf/allstar: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/ossf/allstar.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-33f4-mjch-7fpr (GitHub-reviewed advisory GHSA-33f4-mjch-7fpr lists affected ranges: Go github.com/ossf/allstar >=0 <0.0.0-20250721181116-e004ecb540d6)

Commands are suggestions: review each one before running it.