NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
.NET
.NET NuGet
Not in CISA KEV
CRITICAL severity

Use of Hard-coded Credentials in AgileConfig.ClientGHSA-mj5w-w588-j6xg

CRITICAL

GHSA-mj5w-w588-j6xg is a critical-severity (CVSS 9.8) Hard-coded Credentials vulnerability in AgileConfig.Client. A fix is available for AgileConfig.Client — see the affected versions and patch details below.

Also known asCVE-2022-35540
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.5%probability of exploitation in next 30 days
Lower Risk+0.04%
Lower risk than most CVEs75th percentile — riskier than 75% of all scored CVEsHighest risk
0.06%0.71%1.37%2.02%0.6%1.5%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

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
EcosystemPackageVulnerable rangeFix
.NETNuGetAgileConfig.Clientall versions1.6.8dotnet add package AgileConfig.Client --version 1.6.8

Affected Products

1 product · 1 configurations
Application
agileconfigdotnetcore
< 1.6.8
range

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for AgileConfig.Client, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. 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.

  3. Workarounds

    Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

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?

Find it across NuGet, including transitive dependencies.

Scan my dependencies How O3 SCA works
Use of Hard-coded Credentials in AgileConfig.Client