CVE-2025-35940
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe ArchiverSpaApi ASP.NET application uses a hard-coded JWT signing key. An unauthenticated remote attacker can generate and use a verifiable JWT token to access protected ArchiverSpaApi URL endpoints.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe ArchiverSpaApi ASP.NET application contains a hard-coded JWT signing key embedded in its source code. An unauthenticated remote attacker who discovers this key (which may be obtained through source code access, binary analysis, or other means) can forge valid JWT tokens and use them to access protected API endpoints without legitimate credentials.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if ArchiverSpaApi application is presentSearch for files or directories named 'ArchiverSpaApi' in your environment, including web application directories, deployed binaries, or source code repositories.Affected if The ArchiverSpaApi application or its source code exists in your environment.
-
Locate JWT configuration in source codeSearch source code files (.cs) for JWT-related code patterns such as 'JwtBearer', 'TokenValidationParameters', 'SigningKey', or 'IssuerSigningKey'. Also check appsettings.json and web.config for JWT configuration sections.Affected if JWT configuration files or code references exist in the application.
-
Search for hard-coded secret stringsInspect the application's source code for hard-coded string literals assigned to JWT signing key variables. Look for patterns like 'new SymmetricSecurityKey(Encoding.UTF8.GetBytes(""))' or similar constructs with embedded key strings.Affected if A hard-coded string value is found directly in the source code assigned to a JWT key variable.
-
Examine binary files for embedded secretsIf source code is unavailable, use a hex editor or strings tool to examine the compiled binaries (DLL/EXE files) for the ArchiverSpaApi application. Search for long random-looking strings that may be JWT signing keys.Affected if A long random string resembling a cryptographic key is embedded in the compiled binaries.
Your environment is affected if the ArchiverSpaApi application contains a hard-coded JWT signing key embedded in its source code or compiled binaries.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataReplace the hard-coded JWT signing key with a securely managed secret (e.g., environment variable, key vault, or ASP.NET Secret Manager), update the application to load the key at runtime from the secure source, and rotate the compromised key to prevent continued unauthorized access.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-35940 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-35940 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data