CVE-2026-5728
Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.
Generated by VEDAS. Scores as of 2026-11-01 19:19 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.
What it is
The CVE record is reserved but not yet published on CVE.org, so affected versions, CVSS and references will appear here once it is.
How it can be exploited
Public exploit evidence (Exploit Observer)
Also known as: BDU:2026-06492
VEDAS cluster: VEDAS:FREEZINGGLOW
Exploit Observer links 3 pieces of public exploit code or detection modules that name this CVE or one of its aliases.
Exploit code and modules (3)
Code that names this CVE. A repository can be a working exploit, a scanner, a fake or malware; read it before running anything.
- Code repository: https://raw.githubusercontent.com/ARPSyndicate/vedas-signatures/main/suricata/2026/CVE-2026-5728.rules
- Code repository: https://raw.githubusercontent.com/ARPSyndicate/vedas-signatures/main/suricata/2026/CVE-2026-5728.rules
- Code repository: https://raw.githubusercontent.com/ARPSyndicate/vedas-signatures/main/suricata/2026/CVE-2026-5728.rules
Research and write-ups (1)
- Research or write-up: https://aydinnyunus.github.io/2026/05/03/content-type-spoofing-lollms-chat-image-cve-2026-5728
Vulnerability databases and vendor advisories (1)
Catalogue entries, not exploit evidence.
- Vulnerability database or vendor advisory: https://nvd.nist.gov/vuln/detail/CVE-2026-5728
2 more references returned by Exploit Observer did not name this CVE or an alias, so they are left out.
VEDAS data as of 2026-11-01T17:12 UTC; fetched 2026-11-02.
Live scores
- EPSS
- 0.000
low predicted chance of attack - VEDAS
- 0.971
strong exploit evidence - On CISA KEV
- Not listed
- Detection rule
- Suricata
Who is affected
The CVE record does not list affected products yet.
How to fix it
No fixed version or vendor advisory is listed in the CVE record yet. Watch the vendor’s security page.
How to detect it
Suricata rules (network detection)
1 rule that alert on traffic matching this exploit: VEDAS CVE-2026-5728 LoLLMs - Chat Image Upload Content-Type Spoofing. Add them to your Suricata rule set and reload.
Show the rules
alert http $EXTERNAL_NET any -> $HTTP_SERVERS $HTTP_PORTS (msg:"VEDAS CVE-2026-5728 LoLLMs - Chat Image Upload Content-Type Spoofing"; flow:established,to_server; http.method; content:"POST"; http.uri; content:"/api/upload/chat_image"; nocase; fast_pattern; http.request_body; content:"filename="; nocase; pcre:"/filename=\x22[^\x22]+\x2e(py|php|phtml|phar|js|html|sh|exe|svg)\x22/i"; content:"image/"; nocase; classtype:web-application-attack; reference:cve,CVE-2026-5728; reference:url,https://www.exploit.observer/?keyword=CVE-2026-5728&match=exact; reference:url,https://subdomain.center/?engine=ammonites&keyword=lollms&match=exact; sid:1093003; rev:1;)
References
Other databases
Where this comes from
This advisory is generated automatically by VEDAS from: cve-scores (EPSS and VEDAS), Exploit Observer, vedas-signatures. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.