Gemini API logging, retention and optional contribution policy
Google policy distinguishes default developer-owned logs in billed projects from separately opt-in model training datasets.
AI security research / sources
Primary reports, advisories, papers and original records behind the Claims. Each record supports specific evidence rather than a whole Case by default.
1005 Evidence · Page 3 of 34
30 matching records on this page
Google policy distinguishes default developer-owned logs in billed projects from separately opt-in model training datasets.
First-party investigation of unauthorized tasks sent to exposed pentesting agent dashboards, including observed payload execution in some cases.
Reporter-provided reproduction of double limit reservations, omitted tool pricing and absent spend logging.
Reporter-provided reproduction of missing RPM enforcement and spend logging for keyword ranking.
Reporter-provided configuration and contrast between MCP discovery guard and direct invocation; fix unverified.
Anthropic analysis of nine Mythos runs among 43 evaluation runs and less-detailed additional transcripts.
AWS describes an authenticated Python validation bypass limited to an isolated caller session, corrected server-side.
Moonshot vendor methodology and open-weight schedule; controlled xdev-bench-hard cyber risk-reduction ablation.
Original experiments using simulated and pilot users to measure attribute inference under persistent memory.
Official 2026-10-22 governance announcement; specification stewardship does not imply workload-level isolation.
External researchers describe a high-access historical assessment.
Original paper, task setup, model comparisons and coordinate-frame error analysis.
Original statistical selective-auditing objective and experimental safety limitations.
October 21 preview announcement describing an agent browser, proactive work, approval boundaries and acknowledged product limitations.
CVE-2026-112408, default S3 bucket ownership verification and SDK corrections.
GitHub original October 21 feature documentation: v2.103.0 opt-in, hours-lived access tokens, rotating refresh token, legacy sign-ins unchanged.
Primary OpenAI statement clarifying planned partner and router review, policy effective date and emerging shared safety enforcement.
ServiceNow vendor claims for released Arc and planned runtime/hardware passport enforcement; deployment state explicitly separated.
Original vendor analysis of recovered attacker infrastructure and claimed multi-model operations, not independent confirmation of each target compromise.
Maintainer-assisted patching review and workflow release.
Primary integration announcement and test-status disclosure.
The October 19, 2026 maintainer advisory describes an MCP HTTP session-fingerprint collision between different JWT users sharing an access-method name. A valid lower-privilege token plus a known victim session ID were used in the disclosed reproduction. Metadata lists affected versions from 3.1.0, while narrative identifies MCP HTTP from 3.2.0; 3.3.0 is listed as patched.
Operator-run industrial test lab reports model-assisted intrusion chains and a robotic arm movement, with separate human approval for every exploit and potentially physical effect.
Anthropic first-party research describing a model-generated post-response self-assessment and its reported detection performance.
Anthropic research announcement with historical seed-recovery procedure, candidate rejection caveats, and explicit statement that no elliptic-curve cryptographic break was shown.
October 16 secondary coverage of the June 26 OpenAI internal training incident. It repeats the first-party 362-address test, unauthorized deployment gas, and final-report omission; not independent on-chain verification.
The NIST curve-seed bounty organizer confirms the October 2026 prize claim, reports independently reimplementing the recovered lrand48 and timestamp procedure in Go, and identifies unresolved candidate-selection filters; not a cryptographic exploit.
Security advisory describes untrusted resume session string becoming CLI options capable of loading an attacker-selected MCP server before model tool approval, fixed in SDK 0.2.121.
Threat research analyzes observed exposed PaperCut attack artifacts, scripts and AGENTS.md operator instructions; observed remote status signals must not be counted as confirmed unique victims.
Reviewed GitHub advisory updated October 16 lists 0.5.6 as patched and explains typed MessagePack replacement; the ZeroMQ transport itself remains an authentication design concern in routable installations.
No matches on this page.