CVE-2026-111985
Received Received - Intake

Allocation of Resources via Metadata Extraction in AUTOMATIC1111 stable-diffusion-webui

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

Publication date: 2026-10-18

Last updated on: 2026-10-18

Assigner: VulDB

Description

A vulnerability was found in AUTOMATIC1111 stable-diffusion-webui up to 1.10.1. This impacts the function read_metadata_from_safetensors of the file modules/sd_models.py of the component Metadata Extraction. The manipulation of the argument header length field results in allocation of resources. It is possible to launch the attack remotely. The exploit has been made public and could be used. The project was informed of the problem early through an issue report but has not responded yet.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

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

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
AUTOMATIC1111 stable-diffusion-webui 1.10.0
AUTOMATIC1111 stable-diffusion-webui 1.10.1

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-770 The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.
CWE-400 The product does not properly control the allocation and maintenance of a limited resource.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability exists in AUTOMATIC1111 stable-diffusion-webui versions up to 1.10.1. It involves the function read_metadata_from_safetensors in modules/sd_models.py which fails to validate the header length field in .safetensors files. An attacker can craft a malicious file with an extremely large header length (e.g., 2^40 or 2^46 bytes), causing the application to attempt allocating an impractically large amount of memory (~64 TiB) during model scanning. This leads to a MemoryError and potential denial of service.

Detection Guidance

Check for unusually large memory allocations or errors in logs when processing .safetensors files. Monitor for files with falsified header lengths (e.g., 2^40 or 2^46 bytes) in the models directory. Use the PoC files from Resource 1 to test if your system is vulnerable.

Impact Analysis

The vulnerability can cause denial of service by triggering excessive memory allocation attempts. It may also lead to application instability, repeated error logging, and prevent proper metadata access for models. Since the attack requires only placing a malicious file in the models directory, users could unknowingly trigger this issue by adding certain files to their system.

Compliance Impact

The vulnerability could lead to denial-of-service conditions due to excessive memory allocation, potentially disrupting service availability. This may impact compliance with regulations requiring data availability (e.g., GDPR Article 32, HIPAA Security Rule). However, the provided context does not explicitly link this vulnerability to compliance failures or data breaches.

Mitigation Strategies

Upgrade to a patched version of AUTOMATIC1111 stable-diffusion-webui if available. Remove untrusted .safetensors files from the models directory. Implement safeguards to validate header lengths against file size or delegate parsing to the official safetensors library.

Chat Assistant

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

EPSS Chart