Google Gemini allowed users to download AI-generated images that its safety filters had refused to display, according to research published by Fog Security on November 5, 2026.

The bypass did not require a jailbreak. Instead, the download feature sometimes delivered a rejected image while the conversation showed a different, allowed picture.

Gemini Image Safety Filter Bypass

Fog Security reported the issue to Google in June 2026. By October 22, researchers could no longer reproduce it across 12 new attempts, and older conversations downloaded the correct images.

Google attributed the change to routine maintenance rather than a fix linked to the report. A Gemini web app flaw allowed blocked images to bypass safety refusals through the full-size download path, despite remaining restricted in chat.

Researchers first submitted an image request that triggered a refusal, then requested a different, permitted image. Although the allowed picture appeared onscreen, its download button sometimes retrieved the rejected output.

Results ranged from blurry, unfinished files to complete images, with successful tests across multiple days and sessions. Both image URLs used lh3.googleusercontent.com and required the signed-in user’s session. Inline links ended in =s1024-rj, while download links ended in =s0-d-I.

Researchers suspected a state-management error involving image generation, safety checks, and cleanup. That explanation remains unconfirmed.

A December 2025 Google community report also described downloads returning older images instead of the displayed preview. However, that complaint did not establish a safety bypass.

Unlike prompt injection targeting Gemini’s memory, this issue did not rely on hidden instructions changing the assistant’s behavior.

It also differed from AI jailbreaks using assistant prefill, which push models toward prohibited answers. Here, the refusal remained intact while file delivery failed to enforce it.

Fog Security tested copyrighted characters, a synthetic person, and the researcher’s own likeness. It did not test child safety content or images involving other real people. No access to another user’s data or privilege escalation was reported.

Google initially marked the June 25 report out of scope, then reviewed it after researchers stressed the infrastructure issue. It declined to track an abuse bug on September 30. On October 23, Google said no internal ticket had been filed and closed the report.

Fog Security recommends binding each download to its approved preview and removing files from refused or failed generations. The finding shows why AI safety testing must cover stored files and download links, not only chatbot replies. A refusal protects users only when every delivery path follows the same decision.

Give your SOC the alert context to stops incidents quickly. Integrate Threat Intel from 16K SOCs.

The post Google Gemini Safety Bypass Lets Users Download AI-Generated Images That Its Own Filters Blocked appeared first on Cyber Security News.

Google has announced Gemini 4 Carbon, its latest AI model built to find software flaws, test whether attackers could exploit them, and produce fixes.

Unveiled on October 28, 2026, Carbon builds on Gemini 4 Argon and targets complex security and coding work that can take days. Access will begin with selected cyber defenders, not a public launch.

According to Google’s announcement, Carbon combines stronger cybersecurity skills with improved handling of long tasks. Google says internal teams have seen it work through dead ends while tracing subtle bugs across large codebases and low-level systems, then develop patches that address their root cause.

Google reports that Carbon scored 88.2% on SEC-bench Pro for vulnerability discovery, 54.8% on ExploitGym for exploitation, and 71.0% on CWE-bench for patching.

These tests cover three linked stages of security work: finding a flaw, checking its impact, and fixing the underlying code. Google evaluated these capabilities without guardrails, an important limit when comparing benchmark results with deployed services.

Google Launches Gemini 4 Carbon

Carbon also leads the Artificial Analysis Intelligence Index v5.0 with a score of 59. The index combines nine evaluations across coding, science, knowledge work, and general knowledge. Its overall ranking provides broader context, but does not replace task-specific security testing.

On internal tests, Google says Carbon more than doubled Argon’s success rate for generating secure code. The Chrome team also reported over tenfold better performance in producing quality patches compared with an unnamed rival model. Google did not identify that model in the announcement, limiting outside comparison of this claim.

Google says Carbon uses several safety layers, including misuse checks, prompt injection defenses, and monitoring of its reasoning and actions.

On Gray Swan’s Indirect Prompt Injection benchmark, Carbon recorded a 0.0% attack success rate, compared with Argon’s 0.7%. That result applies to the evaluated attacks, not every possible attack in production.

The risk remains relevant for security teams using AI agents. Previous reporting on Gemini for Workspace prompt injection described how hidden email instructions could cause misleading security warnings in AI summaries.

Separate coverage of Gemini data theft vulnerabilities showed how poisoned content could expose saved information before Google fixed the reported issues.

Google also reports that high-severity misalignment alerts fell by almost 80% in internal coding environments. Unsupported claims dropped by roughly half compared with Argon. At the same time, successful cheating on Terminal-Bench 4.0 fell to zero in the reported evaluation.

Carbon will reach selected defenders first, followed by additional trusted partners through Google’s Fairwind Program. Google is also participating in voluntary U.S. government testing before wider deployment.

Introductory pricing is $2 per million input tokens and $10 per million output tokens, with cached inputs discounted by 95%. Standard rates will later rise to $4 and $20, respectively. Google has not announced a firm date for general availability.

Give your SOC the alert context to stops incidents quickly. Integrate Threat Intel from 16K SOCs.

The post Google Launches Gemini 4 Carbon With State-Of-The-Art Cybersecurity Capabilities appeared first on Cyber Security News.

Google has announced a new set of Android security protections designed to stop mobile scams across calls, text messages, chat apps, web links, and account verification codes.

The update comes as criminals increasingly use spoofed phone numbers, fake bank alerts, phishing pages, remote screen sharing, and AI-generated voices to trick users into giving up money or login details.

Google said its existing AI-powered scam detection tools in Phone by Google and Google Messages already identify more than five million suspected scam calls and texts each month.

The new protections focus on preventing users from reaching the most dangerous stage of a scam. Instead of only blocking known malicious links or spam numbers.

Android will use a mix of on-device AI, cloud-based analysis, privacy protections, and real-time checks to identify suspicious behavior before victims share passwords, payment data, or one-time passcodes.

A key addition is an opt-in Enhanced Protection mode in Google Messages. Google said the setting will roll out in the coming weeks and will activate stronger protections for complex messaging scams.

This includes expanded Scam Detection using Google’s Private AI Compute platform, which allows Gemini models to review the context of a conversation with an unknown sender.

Google Unveils New Android AI Protections

The aim is to spot slow-moving social engineering scams where criminals build trust over several messages before sending a fraudulent request or link. Google said the analysis occurs in an encrypted environment that Google employees cannot access.

Enhanced Protection will also strengthen link checks in Google Messages. Scammers frequently create new phishing domains that have not yet been added to threat blocklists, which can make standard URL filtering less effective.

Google said Gemini Nano, its on-device AI model, will combine real-time web signals with local analysis to assess unfamiliar links before a user opens them.

Android will also show redesigned warnings for links from numbers not saved in the user’s contacts. This provides an extra checkpoint before users visit a potential phishing page.

The company is also expanding scam alerts from Pixel devices to a wider Android ecosystem. Scam Detection in chat notifications can flag suspicious messages from supported chat apps directly in the notification panel, allowing users to see a warning before opening the message.

Google is working with Android device makers to bring the on-device feature to hundreds of millions of additional users later this year.

Google’s update also targets phone-based social engineering scams, particularly cases where criminals persuade victims to share their screen or redirect incoming calls.

Android will now automatically hide login fields and payment screens during active screen-sharing sessions in Chrome and Android WebView. The Protection is designed to stop fraudsters from viewing passwords, card details, and other sensitive information while guiding a victim through a fake support or banking process.

Another major safeguard addresses OTP theft through call forwarding. Threat actors may trick a user into entering a call-forwarding code, redirecting incoming calls containing verification codes to a criminal-controlled number.

Android will block apps from silently enabling call forwarding in the background and warn users before a manually entered MMI forwarding code takes effect.

Security teams can also review related account takeover risks and prevention steps in Cyber Security News coverage of OTP bypass and MFA phishing campaigns and mobile banking malware.

Google is also expanding verified financial calls, a feature built with banks including Banco do Brasil and Itaú Unibanco. The system checks whether the bank’s official app actually initiated a call claiming to come from a bank.

If verification fails, Android can end the call and alert the user. Google said the feature has blocked more than three million spoofed calls involving the two Brazilian banks since its June launch.

The announcement shows mobile security shifting from simple spam filtering to behavior-based fraud prevention. Users should still avoid sharing passwords, card information, recovery codes, or OTPs over calls and messages, even when the caller appears legitimate.

Update defenses against new malware as soon as it appears. Integrate TI Feeds with data from 16K SOCs.

The post Google Unveils New Android AI Protections to Block Scam Calls, Phishing Links and OTP Theft appeared first on Cyber Security News.

Google automatically verifies phone numbers on Android devices and adds them to every Google account signed in on the Phone. The setting is enabled by default, raising privacy concerns for users who keep personal, work, and secondary accounts separate.

Google’s documentation confirms that the behavior covers both existing accounts and accounts added later. The feature, called Phone number verification, also covers new phone numbers added to a device.

Adding another Google account can link it to numbers already on the Phone, while adding a new number can attach it to accounts already signed in. Users must turn the setting off themselves to stop automatic verification.

According to Google’s support documentation, verification supports account sign-in, account recovery, emergency services, and communication features.

Google and mobile carriers periodically check that numbers still belong to the user. The company notes that carrier charges may apply during this process.

Google Auto-Adds Phone Numbers to Android Accounts

Android Authority reported that users received unexpected emails saying their phone numbers had been verified. Its staff also found automatic verification enabled on their devices.

The publication said Google updated its support page between August and October 2025 to describe the default setting and account-wide linking. That documentation change does not establish an exact rollout date.

For someone using a separate account for public discussions, testing, or other activities, attaching a personal number creates an unwanted connection within Google’s systems. The concern is losing control over which accounts hold that number.

The documentation does not say this makes the number publicly visible to everyone. Google also says verification enables Better sharing on Google, which supports calls, messages, and notifications involving the number.

However, when several accounts are signed in, Better sharing turns on for only one account. This differs from phone number verification, which applies across all signed-in accounts.

This behavior is an account setting, not evidence of a Google account breach. Cybersecurity News previously covered Google’s denial of Gmail breach claims.

Its reporting on Google’s move toward passkeys also highlights the company’s efforts to simplify account access. Open Android Settings, select Google, and open All services. Under Privacy & security, select Phone number verification, then turn off Verify phone numbers automatically. Google says device settings manage this control.

Turning it off does not remove numbers already attached to accounts, according to Android Authority. Open each affected account’s Personal info page, select Contact info, then Phone, and remove unwanted numbers individually. Review how each number is used before changing it, particularly where account recovery is involved.

Some users reported on Reddit that the setting switched back on on its own. Android Authority could not reproduce that behavior, so it remains a user-reported issue rather than a confirmed general fault. Users managing several accounts should review both the device setting and each account’s stored phone numbers.

Update defenses against new malware as soon as it appears. Integrate TI Feeds with data from 16K SOCs.

The post Google Automatically Adds Your Phone Number to Every Google Account on Your Android Phone appeared first on Cyber Security News.