NewsBleepingComputer
Gemini AI agents repeatedly bypassed safeguards to attack real website
Teaser from the source
Google's Gemini AI agents repeatedly attempted to hack a real organization's website during AI model safety testing, finding ways to circumvent increasingly restrictive security controls designed to prevent them from accessing live systems. [...]
This is the RSS-feed teaser. Read the full article at the original source.
Read at BleepingComputerMore on repeatedly
Other advisories
- HighCVE-2026-126190Soup Sieve is a CSS selector library designed to be used with Beautiful Soup 4. Prior to 4.0, Soup Sieve repeatedly walks the same ancestors while matching d…
- MediumCVE-2026-126189Soup Sieve is a CSS selector library designed to be used with Beautiful Soup 4. Prior to 4.0.1, Soup Sieve repeatedly searches descendant subtrees for each c…
- MediumCVE-2026-125040A flaw was found in the SRT and WebVTT subtitle parser in GStreamer's gst-plugins-base. While sanitizing inline subtitle markup, the parser repeatedly search…
- MediumCVE-2026-100350kin-openapi deepObject query decoding repeatedly compiles an invariant regular expression in github.com/getkin/kin-openapi
- HighCVE-2026-119196pyasn1 is a generic ASN.1 library for Python. Prior to 0.6.5, constructed BIT STRING decoding repeatedly shifts and copies the complete bit value accumulated…
- HighCVE-2026-119195pyasn1 is a generic ASN.1 library for Python. Prior to 0.6.5, constructed string and indefinite-length ANY decoding repeatedly concatenates each fragment ont…
- HighCVE-2026-117540svg-sanitizer from 0.5.3 before 1.1.0 contains a denial of service vulnerability in Sanitizer::sanitize() that repeatedly rescans the whole input while strip…
- HighCVE-2026-110354HAProxy 3 before 3.4.6 allows a remote unauthenticated attacker to cause a denial of service (persistent worker-thread CPU exhaustion) via an HTTP/1.1 chunked request. Although the H1 multiplexer drains the request before closing the stream, the parser repeatedly re-processes the same bytes without making progress. The affected thread stays busy at 100% CPU after timeouts expire and after the client disconnects, and repeated requests can consume all worker threads until the process is restarted.
Other news entries
- British soldier ignored order to pull his SIM card, then got blackmailedNewsArs Technica — Security
- Attackers Tampered with AOMEI Backupper's Update Servers for Minutes to Deliver a BackdoorNewsThe Hacker News
- AWS’s repeated problems with AI agent controls illustrates the autonomous agent dilemmaNewsCSO Online
- European Parliament Member Investigating Spyware Was Hacked With PegasusNewsThe Hacker News
ID