How severe is GHSA-6xhf-x49c-m5m6?

No CVSS score has been assigned to GHSA-6xhf-x49c-m5m6 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-6xhf-x49c-m5m6?

GHSA-6xhf-x49c-m5m6 affects the following packages: aegir (npm). Ecosystems affected: npm.

How do I fix GHSA-6xhf-x49c-m5m6?

Update aegir to 12.0.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6xhf-x49c-m5m6 is resolved across your whole dependency graph.

How do I detect GHSA-6xhf-x49c-m5m6 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for aegir. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-6xhf-x49c-m5m6 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-6xhf-x49c-m5m6?

O3 pinpoints whether GHSA-6xhf-x49c-m5m6 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-6xhf-x49c-m5m6 actively exploited in the wild?

No public exploit code has been indexed for GHSA-6xhf-x49c-m5m6 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What type of vulnerability is GHSA-6xhf-x49c-m5m6?

GHSA-6xhf-x49c-m5m6 is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-6xhf-x49c-m5m6 published, and has it been updated?

GHSA-6xhf-x49c-m5m6 was published on July 24, 2018 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

GHSA-6xhf-x49c-m5m6

GHSA-6xhf-x49c-m5m6 is a Information Exposure vulnerability in aegir. O3 Security confirms whether GHSA-6xhf-x49c-m5m6 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Github Token Leak in aegir

Also known asCVE-2017-16225

Published

Jul 24, 2018

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 8, 2023 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

33other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

aegirnpm

9Kdownloads / week

Description

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`aegir`	≥ 12.0.0&&< 12.0.8	12.0.8

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for aegir. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update aegir to 12.0.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6xhf-x49c-m5m6 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-6xhf-x49c-m5m6 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-6xhf-x49c-m5m6. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is GHSA-6xhf-x49c-m5m6 in your dependencies?

O3 detects GHSA-6xhf-x49c-m5m6 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works