Authorization Bypass Through User-Controlled Key in go-zero

Exploitation

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

CVSS

9.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

EPSS

• CVE-2024-27302: 0.77% estimated exploitation activity in the next 30 days; percentile 55.81 (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.

Summary Hello go-zero maintainer team, I would like to report a security concerning your CORS Filter feature. Details Go-zero allows user to specify a CORS Filter with a configurable allows param - which is an array of domains allowed in CORS policy. However, the isOriginAllowed uses strings.HasSuffix to check the origin, which leads to bypass via domain like evil-victim.com PoC Use code below as a PoC. Only requests from safe.com should bypass the CORS Filter Send a request to localhost:8888 with Origin:not-safe.com You can see the origin reflected in response, which bypass the CORS Filter Impact This vulnerability is capable of breaking CORS policy and thus allowing any page to make requests, retrieve data on behalf of other users.

Published by the source

4 Mar 2024, 20:42 UTC

Last modified by the source

24 Mar 2026, 05:02 UTC

Source last checked

26 Oct 2026, 15:18 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-fgxv-gw55-r5fq

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

# Patch Next advisory brief: CVE-2024-27302

Advisory: Authorization Bypass Through User-Controlled Key in go-zero
IDs: CVE-2024-27302, GHSA-fgxv-gw55-r5fq
Record: https://patchnext.com/advisories/cve-2024-27302 (revision 1, source checked 26 Oct 2026, 15:18 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/zeromicro/go-zero 1.4.4. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/zeromicro/go-zero: affected < 1.4.4; fixed in 1.4.4

## Suggested inspection (read-only)
- Go github.com/zeromicro/go-zero: 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/zeromicro/go-zero.
- 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-fgxv-gw55-r5fq (GitHub-reviewed advisory GHSA-fgxv-gw55-r5fq lists affected ranges: Go github.com/zeromicro/go-zero >=0 <1.4.4)

Commands are suggestions: review each one before running it.