How severe is GHSA-mj5w-w588-j6xg?

GHSA-mj5w-w588-j6xg has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-mj5w-w588-j6xg?

GHSA-mj5w-w588-j6xg affects the following packages: AgileConfig.Client (NuGet). Ecosystems affected: NuGet.

How do I fix GHSA-mj5w-w588-j6xg?

Update AgileConfig.Client to 1.6.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mj5w-w588-j6xg is resolved across your whole dependency graph.

How do I detect GHSA-mj5w-w588-j6xg in my NuGet dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for AgileConfig.Client. 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-mj5w-w588-j6xg 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-mj5w-w588-j6xg?

O3 pinpoints whether GHSA-mj5w-w588-j6xg 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-mj5w-w588-j6xg actively exploited in the wild?

No public exploit code has been indexed for GHSA-mj5w-w588-j6xg 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-mj5w-w588-j6xg?

GHSA-mj5w-w588-j6xg is classified as Hard-coded Credentials (CWE-798). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-mj5w-w588-j6xg published, and has it been updated?

GHSA-mj5w-w588-j6xg was published on August 19, 2022 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.

.NET NuGet

GHSA-mj5w-w588-j6xg

CRITICAL

GHSA-mj5w-w588-j6xg is a critical-severity (CVSS 9.8) Hard-coded Credentials vulnerability in AgileConfig.Client. O3 Security confirms whether GHSA-mj5w-w588-j6xg is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Use of Hard-coded Credentials in AgileConfig.Client

Also known asCVE-2022-35540

Published

Aug 19, 2022

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

.NETAgileConfig.Client

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects NuGet packages — download data is not available via public APIs for these ecosystems.

Description

Hardcoded JWT Secret in AgileConfig <1.6.8 Server allows remote attackers to use the generated JWT token to gain administrator access.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
.NETNuGet	`AgileConfig.Client`	all versions	1.6.8

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for AgileConfig.Client. 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 AgileConfig.Client to 1.6.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mj5w-w588-j6xg 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-mj5w-w588-j6xg 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-mj5w-w588-j6xg. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Hardcoded JWT Secret in AgileConfig <1.6.8 Server allows remote attackers to use the generated JWT token to gain administrator access.

O3 Security · Impact-Aware SCA

Is GHSA-mj5w-w588-j6xg in your dependencies?

O3 detects GHSA-mj5w-w588-j6xg across NuGet 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