Reject unauthorized access with GitHub PATs

Exploitation

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

CVSS

7.5 · CVSS:3.1/AV:A/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:L

EPSS

• CVE-2021-21432: 0.99% estimated exploitation activity in the next 30 days; percentile 62.43 (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.

Impact What kind of vulnerability is it? Who is impacted? The additional auth mechanism added within https://github.com/go-vela/server/pull/246 enables some malicious user to obtain secrets utilizing the injected credentials within the ~/.netrc file. Steps to reproduce 1. Create Vela server 2. Login to Vela UI 3. Promote yourself to Vela administrator - UPDATE users SET admin = 't' WHERE name = <username 4. Activate repository within Vela 5. Add .vela.yml to the repository with the following content 1. Look at build logs to find the following content 1. Copy the password to be utilized in some later step 1. Add secret(s) to activated repo 1. Copy the following script into main.go 1. Run the main.go with environment specific settings - VELASERVERADDR=http://localhost:8080 VELATOKEN=<token obtained previously go run main.go The previously posted script could be updated to utilize any API endpoint(s) the activated user has access against. Patches Has the problem been patched? What…

Published by the source

15 Feb 2022, 01:57 UTC

Last modified by the source

2 Oct 2023, 13:09 UTC

Source last checked

26 Oct 2026, 14:59 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-8j3f-mhq8-gmh4

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

# Patch Next advisory brief: CVE-2021-21432

Advisory: Reject unauthorized access with GitHub PATs
IDs: CVE-2021-21432, GHSA-8j3f-mhq8-gmh4
Record: https://patchnext.com/advisories/cve-2021-21432 (revision 1, source checked 26 Oct 2026, 14:59 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/go-vela/server 0.7.5. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/go-vela/server: affected >= 0.7.0, < 0.7.5; fixed in 0.7.5

## Suggested inspection (read-only)
- Go github.com/go-vela/server: 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/go-vela/server.
- 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-8j3f-mhq8-gmh4 (GitHub-reviewed advisory GHSA-8j3f-mhq8-gmh4 lists affected ranges: Go github.com/go-vela/server >=0.7.0 <0.7.5)

Commands are suggestions: review each one before running it.