Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unratedamended

Github Token Leak in aegir

CVE-2017-16225GHSA-6xhf-x49c-m5m6

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (aegir 12.0.8), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm aegir

    Affected
    >= 12.0.0, <= 12.0.7
    Fixed in
    12.0.8

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
not scored
EPSS
  • CVE-2017-16225: 1.16% estimated exploitation activity in the next 30 days; percentile 67.13 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Affected versions of aegir bundle and publish the current users github token to npm when aegir-release is executed. Recommendation Update to version 12.0.8 or later. If you used this module to do a release for your project you should invalidate the GitHub tokens that were leaked.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-6xhf-x49c-m5m6

  2. Revision 1 · created ·

    Published from osv record GHSA-6xhf-x49c-m5m6

Agent brief

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

# Patch Next advisory brief: CVE-2017-16225

Advisory: Github Token Leak in aegir
IDs: CVE-2017-16225, GHSA-6xhf-x49c-m5m6
Record: https://patchnext.com/advisories/cve-2017-16225 (revision 2, source checked 26 Oct 2026, 12:07 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: aegir 12.0.8. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm aegir: affected >= 12.0.0, <= 12.0.7; fixed in 12.0.8

## Suggested inspection (read-only)
- `npm ls aegir --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## 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 aegir.
- 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://osv.dev/vulnerability/GHSA-6xhf-x49c-m5m6 (OSV record GHSA-6xhf-x49c-m5m6 lists affected ranges: npm aegir >=12.0.0 <12.0.8 (fixed))
- Verified: https://github.com/advisories/GHSA-6xhf-x49c-m5m6 (GitHub-reviewed advisory GHSA-6xhf-x49c-m5m6 lists affected ranges: npm aegir >=12.0.0 <=12.0.7)

Commands are suggestions: review each one before running it.

Loading voting…