CVE-2026-73969
Received Received - Intake

Hard-Coded JWT Secret in AnsibleForms

Vulnerability report for CVE-2026-73969, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-11-18

Last updated on: 2026-11-18

Assigner: GitHub, Inc.

Description

AnsibleForms is a self-hosted web application that turns automation into self-service forms. Prior to 6.2.1, AnsibleForms uses a public hard-coded fallback JWT signing secret from server/config/auth.config.js when ACCESS_TOKEN_SECRET is unset. An unauthenticated attacker can sign a self-contained token with privileged claims because server/src/auth/auth_jwt.js verifies the signature without reloading the user from the database, and server/src/lib/middleware.js trusts the token's roles and options for authorization. A forged token can therefore be accepted as an administrator session, resulting in authentication bypass and full privileged API access. This issue is fixed in version 6.2.1.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-18
Last Modified
2026-11-18
Generated
2026-11-19
AI Q&A
2026-11-19
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 3 associated CPEs
Vendor Product Version / Range
ansibleforms ansibleforms to 6.2.1 (inc)
ansibleforms ansibleforms to 6.2.1 (exc)
ansibleforms ansibleforms From 6.2.1 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-1188 The product initializes or sets a resource with a default that is intended to be changed by the product's installer, administrator, or maintainer, but the default is not secure.
CWE-798 The product contains hard-coded credentials, such as a password or cryptographic key.
CWE-287 When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability affects AnsibleForms, a self-hosted web app for automation forms. When the ACCESS_TOKEN_SECRET is not set, it uses a hard-coded fallback JWT signing secret. An attacker can forge a token with privileged claims because the system verifies the signature without reloading user data from the database. This allows authentication bypass and full privileged API access.

Detection Guidance

Check if AnsibleForms is running version 6.2.0 or earlier. Inspect server/config/auth.config.js for a hard-coded JWT secret like 'j6fz%Q9S2YJC?x|u'. Verify if ACCESS_TOKEN_SECRET is unset in the environment or .env file. Look for logs indicating use of an auto-generated temporary secret.

Impact Analysis

An unauthenticated attacker can gain administrator-level access to the AnsibleForms API without credentials. This could lead to full system compromise, unauthorized data access, or further attacks like remote code execution if combined with other vulnerabilities.

Compliance Impact

This vulnerability likely violates compliance requirements for data protection (GDPR, HIPAA) due to unauthorized access risks. It enables breaches of confidentiality and integrity, potentially exposing sensitive user or health data without proper authentication controls.

Mitigation Strategies

Upgrade AnsibleForms to version 6.2.1 or later. Set a strong, unique ACCESS_TOKEN_SECRET in the environment or .env file. Ensure the application fails to start if the secret is unset. Rotate all existing JWT tokens after upgrading and setting the new secret.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-73969. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...