dbcve.org
Improper AuthenticationWeakness · CWE-287

CVE-2026-42869

CRITICAL · 10.0 CVSS v3.1 Published 2026-05-11
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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 · unedited
SOCFortress CoPilot focuses on providing a single pane of glass for all your security operations needs. Prior to 0.1.57, SOCFortress CoPilot ships a hardcoded JWT signing secret as a fallback value in backend/app/auth/utils.py:28 and ships it verbatim in .env.example. Any deployment where JWT_SECRET is not explicitly set — including the default Docker Compose setup — signs all authentication tokens with this publicly known value. An unauthenticated attacker can forge arbitrary admin-scoped JWTs and gain full control of the application and every security tool it manages without any credentials. This vulnerability is fixed in 0.1.57.

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 confidence

SOCFortress CoPilot versions prior to 0.1.57 contain a hardcoded JWT signing secret in backend/app/auth/utils.py that is also shipped in .env.example. Deployments where JWT_SECRET is not explicitly set—including default Docker Compose—use this publicly known secret to sign all authentication tokens, allowing unauthenticated attackers to forge arbitrary admin-scoped JWTs and gain full application control.

MitigationUpgrade to version 0.1.57 or later and explicitly set a unique JWT_SECRET environment variable in all production deployments; also rotate any potentially compromised secrets and invalidate existing sessions.

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
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify CoPilot version
    Locate the version file or Docker image tag used in your deployment. Common locations include a version.txt file, package.json, docker-compose.yml version labels, or the CoPilot web UI footer.
    Affected if The installed version is lower than 0.1.57.
  2. Locate JWT_SECRET configuration
    Check your environment configuration files (.env, .env.production) and running container environment variables for the JWT_SECRET setting. Run 'echo $JWT_SECRET' on running containers or inspect your deployment's environment file.
    Affected if JWT_SECRET is not defined, empty, or set to the default value from .env.example.
  3. Inspect auth/utils.py for hardcoded secret
    Examine the file backend/app/auth/utils.py in your deployment, specifically around line 28. Look for any hardcoded string assigned to JWT_SECRET or used as a signing key.
    Affected if A hardcoded secret value is present in the source code at line 28.
  4. Verify Docker Compose default configuration
    If using Docker Compose, review your docker-compose.yml and any accompanying .env file. Determine whether JWT_SECRET was explicitly configured or if the deployment relies on defaults.
    Affected if The deployment uses default Docker Compose settings without a custom JWT_SECRET defined in the .env file.

You are affected if your CoPilot version is below 0.1.57 AND JWT_SECRET was not explicitly set in your environment, allowing the publicly known hardcoded secret to be used for token signing.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Upgrade to version 0.1.57 or later and explicitly set a unique JWT_SECRET environment variable in all production deployments; also rotate any potentially compromised secrets and invalidate existing sessions.

Recommended fix High confidence

Upgrade to version 0.1.57 or later

  1. Upgrade SOCFortress CoPilot to version 0.1.57 or later
  2. After upgrade, ensure JWT_SECRET environment variable is explicitly set to a strong, unique value in your deployment configuration
  3. Verify the application is using the new JWT_SECRET by generating a test token and confirming it cannot be forged with the old hardcoded secret
  4. If using Docker Compose, update your docker-compose.yml to include a JWT_SECRET variable with a secure random value

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the patch applied

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-42869 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-42869 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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