CWE · MITRE source
CWE-1427Improper Neutralization of Input Used for LLM Prompting
The product uses externally-provided data to build prompts provided to large language models (LLMs), but the way these prompts are constructed causes the LLM to fail to distinguish between user-supplied inputs and developer provided system directives.
When prompts are constructed using externally controllable data, it is often possible to cause an LLM to ignore the original guidance provided by its creators (known as the "system prompt") by inserting malicious instructions in plain human language or using bypasses such as special characters or tags. Because LLMs are designed to treat all instructions as legitimate, there is often no way for the model to differentiate between what prompt language is malicious when it performs inference and returns data. Many LLM systems incorporate data from other adjacent products or external data sources like Wikipedia using API calls and retrieval augmented generation (RAG). Any external sources in use that may contain untrusted data should also be considered potentially malicious.
Last updated: 15 October 2026 14:21 UTC
NIST 800-53 r5 controls PROPOSED for this weakness (0)AI-assisted
These are model PROPOSALS, not graded mappings. They come
from controls_to_cwe_proposals, which carries no grade field at
all; across the CWE pages 1,540 of 1,722 such associations (89%) have never
been graded by anything. The heading said “address” until
2026-09-29, which asserted a relationship the data does not carry.
Graded cross-walks are on the framework map, not here.
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
| No NIST controls proposed yet. | |||
Top CVEs of this weakness type, ranked by Risk Priority
| CVE | Risk | CVSS | EPSS | Published |
|---|---|---|---|---|
CVE-2023-29374 UPD CR | 9.1 | 9.8 | 0.3965 | 2023-04-05 |
CVE-2024-8309 CR | 8.3 | 9.8 | 0.1374 | 2024-10-29 |
CVE-2026-61447 CR | 7.8 | 10.0 | 0.0249 | 2026-07-11 |
CVE-2026-27966 CR | 7.7 | 9.8 | 0.0255 | 2026-02-26 |
CVE-2023-38896 UPD CR | 7.6 | 9.8 | 0.0184 | 2023-08-15 |
CVE-2023-39661 UPD CR | 7.6 | 9.8 | 0.0142 | 2023-08-15 |
CVE-2026-26015 UPD CR | 7.6 | 9.8 | 0.0154 | 2026-04-29 |
CVE-2026-61539 UPD CR | 7.6 | 10.0 | 0.0123 | 2026-08-21 |
CVE-2026-37003 UPD CR | 7.6 | 9.8 | 0.0132 | 2026-08-27 |
CVE-2026-61732 CR | 7.6 | 10.0 | 0.0122 | 2026-09-24 |
CVE-2024-23752 UPD CR | 7.5 | 9.8 | 0.0101 | 2024-01-22 |
CVE-2024-5826 UPD CR | 7.5 | 9.8 | 0.0088 | 2024-06-27 |
CVE-2024-12366 UPD CR | 7.5 | 9.8 | 0.0121 | 2025-02-11 |
CVE-2025-32711 UPD CR | 7.5 | 9.3 | 0.0803 | 2025-06-11 |
CVE-2025-54795 UPD CR | 7.5 | 9.8 | 0.0100 | 2025-08-05 |
CVE-2026-30741 CR | 7.5 | 9.8 | 0.0123 | 2026-03-11 |
CVE-2026-30306 UPD CR | 7.5 | 9.8 | 0.0098 | 2026-03-30 |
CVE-2026-30308 UPD CR | 7.5 | 9.8 | 0.0098 | 2026-03-30 |
CVE-2026-30310 UPD CR | 7.5 | 9.8 | 0.0097 | 2026-03-31 |
CVE-2026-73487 UPD CR | 7.5 | 9.8 | 0.0096 | 2026-08-13 |
CVE-2025-46059 UPD CR | 7.4 | 9.8 | 0.0072 | 2025-07-29 |
CVE-2026-33654 UPD CR | 7.4 | 9.8 | 0.0072 | 2026-03-27 |
CVE-2026-25879 UPD CR | 7.4 | 9.8 | 0.0069 | 2026-06-01 |
CVE-2026-42074 UPD CR | 7.4 | 9.8 | 0.0072 | 2026-06-02 |
CVE-2026-70477 UPD CR | 7.4 | 9.8 | 0.0081 | 2026-08-04 |