Google Bard
Records
1
Disclosed CVEs
0
Exploited (sev 3–4)
0
CISA KEV flagged
0
Newest record 2025-04-22 · 0 distinct CVE ids · open in the explorer (the explorer matches the first product a record names, so it can list fewer)
Patch now: confirmed exploitation or KEV · 0
Records at severity 3–4 (exploitation confirmed by CISA, the vendor or reporting) and records flagged as listed in CISA KEV. The KEV flag is the classifier’s cisa-kev tag or a source on the KEV catalog; it is recorded when the collector sees the listing, so a missing flag does not mean a CVE is absent from the catalog.
No record for Google Bard has confirmed exploitation or a KEV flag.
Disclosures by month · last 24 months
Nov ’240 disclosedOct ’26
Disclosed CVEs, no confirmed exploitation · 0
No disclosed CVEs without confirmed exploitation.
Other incidents: research and unexploited reports · 1
- 2025-04-22Google Bard Conversation Exfiltration via Indirect Prompt Injection1 Researchindirect-prompt-injection · data-exfiltration · bard
This page lists what has been reported, not what to do about it. Versions and fixes are in each linked advisory; check the vendor’s own advisory before acting.