CVE-2026-109237
Received Received - Intake

Crawl4AI Untrusted Config Bypass Leading to Admin JWT Forgery

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

Publication date: 2026-10-12

Last updated on: 2026-10-12

Assigner: VulnCheck

Description

Crawl4AI from 0.9.0 before 0.9.4 contains an untrusted-config gate bypass that allows non-admin API clients to construct forbidden config objects by wrapping them in dict-type wrappers. Attackers can send a laundered LLMConfig with api_token set to an env reference via /config/dump to read SECRET_KEY and provider keys, enabling admin JWT forgery.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-12
Last Modified
2026-10-12
Generated
2026-10-12
AI Q&A
2026-10-12
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
unclecode crawl4ai 0.9.0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-502 The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-109237 is a security flaw in the crawl4ai library versions 0.9.0 to 0.9.3. It allows unauthenticated attackers to bypass security checks by wrapping forbidden configuration objects in dictionary-type structures. This bypasses the untrusted-config gate, enabling access to sensitive environment variables like SECRET_KEY and LLM API keys (e.g., OPENAI_API_KEY). Attackers can then forge admin JWT tokens if SECRET_KEY is compromised.

Detection Guidance

Check if your Crawl4AI version is between 0.9.0 and 0.9.3. Inspect API logs for requests to /config/dump with wrapped dict-type objects. Look for environment variable leaks in responses or logs.

Impact Analysis

This vulnerability allows attackers to read sensitive environment variables such as SECRET_KEY and LLM API keys. If SECRET_KEY is exposed, attackers can forge admin-scope JWT tokens, gaining unauthorized administrative access. Additionally, it may enable arbitrary file writes through deserialized objects.

Mitigation Strategies

Upgrade to Crawl4AI version 0.9.4 or later immediately. Avoid storing SECRET_KEY in the environment. Restrict API access to trusted clients only. Remove unnecessary secrets from the server environment.

Chat Assistant

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

EPSS Chart