Search This Blog

Powered by Blogger.

Blog Archive

Labels

Footer About

Footer About

Labels

Showing posts with label Vulnerability Research. Show all posts

AI Spam Surge Forces Google to Pause Open Source Bug Bounty Program


OSS VRP (Open Source Software Vulnerability Rewards Program) has temporarily been suspended after a sharp increase in automated reports that were found to be valid. Since October 1, security teams and open-source maintainers have been facing an increasing number of low-quality vulnerability reports generated via artificial intelligence. 


The pause, which took effect on October 1, is in response to increasing volumes of low-quality vulnerability reports. Google announced the OSS VRP in August 2022 as a means of rewarding researchers who identifies and responsibly discloses security flaws in open-source software maintained by the company. 

The program covers projects such as Golang, Angular, Bazel, Protocol Buffers and Fuchsia, along with selected third-party dependencies. Security concerns regarding GitHub Actions, application configurations, repository settings, and access control rules are also covered by this program. There was initially a range of rewards available from $100 to $31,337 under the program, with particular emphasis placed on vulnerabilities that could potentially pose significant risks for software suppliers. 

As a result of the company's wider vulnerability rewards program, millions of dollars have since been awarded to researchers, making the OSS VRP an important means of identifying security vulnerabilities in widely used open-source projects. An increase in automated submissions was responsible for the current suspension, according to the company, with the majority failing to identify valid security issues. 

Although the use of artificial intelligence-assisted tools has made the generation of vulnerability reports at scale easier, the resulting volume may also include incorrect findings, duplicate claims, and reports concerning vulnerabilities that do not exist. OSS VRP is currently being reviewed by Google to address the issue and determine how the program should handle the growing number of automated submissions. 

A further update is anticipated in the first quarter of 2027. Additionally, the company clarifies that the change does not affect outstanding reports or product vulnerabilities submitted prior to October 1. The impact of the AI-driven reporting surge extends beyond Google's program as well. 


It has not been the company's first time experiencing a sharp increase in low-quality vulnerability submissions that have been generated by automated tools. This raises concerns about the time security teams will need to spend validating reports that do not identify genuine vulnerabilities. The Google Patch Rewards Program continues to offer incentives to researchers for submitting high-impact open-source security patches that qualify for rewards of up to $15,000. 

Google Cloud's Cloud Vulnerability Reward Program provides a means of reporting security vulnerabilities affecting open-source repositories related to Google Cloud products. Google's decision follows similar developments elsewhere in the security industry. In January, the curl project maintainer terminated its HackerOne bug bounty program in response to a significant number of low-quality, artificial intelligence-generated vulnerability reports. 

As part of its Intigriti bug bounty program, Intel also removed financial rewards in September, though the company did not provide a publicly stated reason for the change. As the use of artificial intelligence tools increases in speed, potential vulnerabilities are identified and reported more rapidly, while the review process remains the responsibility of security researchers and maintainers. 

Earlier this year, Microsoft warned that AI-assisted vulnerability discovery could increase the number and scale of security discoveries, potentially increasing the operational demands on security teams. Google has not yet confirmed that the Open Source OSS VRP will be permanently discontinued. The company is reviewing the program and anticipates making changes in the first quarter of 2027. 

For now, the temporary suspension reflects a growing challenge for bug bounty programs, namely, how to handle a large volume of automated reports without allowing invalid findings to overwhelm genuine security issues. 

The decision of Google highlights the difficulty of vulnerability reward programs as AI-assisted security research increases submissions. It will become increasingly important for these programs to distinguish genuine findings from automated and inaccurate reports in order for them to be effective.

Google Introduces Gemini 4 Argon With Guardrail-Free Access for Defenders

A new frontier artificial intelligence model, Gemini 4 Argon, has been introduced by Google through its Fairwind Program for initial distribution to trusted cybersecurity defenders. In addition to internal security teams using this model, the company expects wider access as it collects feedback from early users. 

As a software engineering, enterprise knowledge work, and cybersecurity operations solution, Argon is designed to handle complex software engineering and knowledge management tasks. A model developed by Google will be able to identify, validate and patch critical vulnerabilities independently in security environments, thereby expanding the use of artificial intelligence for vulnerability research and remediation. 

Argon will be available to trusted defenders and the company's own teams without cyber-specific guardrails, according to the company. As part of this approach, vetted security professionals will be given full access to the model's capabilities when investigating and addressing threats. In September, Fairwind, a limited access AI security tool for governments, Google Cloud customers and cybersecurity partners, launched.

A significant finding has already been made as a result of its early deployment, Wiz, which is using Argon as part of its Scan for Good initiative, reported that it identified a previously unknown critical vulnerability in healthcare software used by hospitals worldwide. The vulnerability may expose sensitive personal information, although Google has not disclosed the name of the affected software or whether the issue has been resolved. 

Google also reports significantly improved vulnerability detection performance compared with Gemini 3.8 Flash Cyber. A security test conducted by Argon on complex codebases identified security weaknesses, while a test conducted by Wiz on live web applications demonstrated improvements in attack surface discovery, vulnerability identification, and proof-of-concept generation. 

A phased approach is being taken by Google to the wider release, with the model currently restricted to internal teams and vetted defenders. Moreover, the company is participating in the U.S. government's voluntary pre-release process and will refine its safeguards after receiving feedback from early testers in order to broaden the availability to developers, enterprises, and individuals. 

Argon will be designed to reject requests attempting to support cyber or chemical, biological, radiological, and nuclear attacks as part of its broader rollout, while also preserving the support of legitimate dual-purpose research as part of its broader rollout. Additionally, Google is monitoring the model's internal activity for signs of misuse. Indirect prompt injection is also being investigated. 

In Google's opinion, Argon is protected against attempts to manipulate it through malicious instructions or external content. The Fairwind program provides another layer of control around access by monitoring the model’s reasoning and actions, and stopping execution when behavior goes beyond the intended task. 

Organizations participating in the program have been vetted and their use has been restricted to authorized defense activities such as threat simulation, reverse engineering, and malware analysis for research or security purposes. Partners are not permitted to share or distribute access to the model. Google has not provided a date of general availability yet. 

Upon initial deployment of Argon Defender, API customers and Google AI Ultra subscribers should have access, although the broader deployment of Argon will be dependent on the results of ongoing safety and security evaluations.

Vercel Sandbox Challenge Uncovers Linux Kernel Flaws


 Vercel has conducted a two-week security challenge that has uncovered numerous vulnerabilities in the Linux kernel networking stack that is used by its Firecracker microVM sandbox. This program, supported by a $1 million reward pool, examined researchers' abilities to break out of an environment that isolates untrusted artificial intelligence-agent code from other software. There were 1,285 vulnerability reports generated as a result of the challenge running from August 18 to September 1. 


There have been about $325,000 in payouts to date for one critical, seven high-severity, 15 medium-severity, 49 low-severity and 19 informative findings validated by Vercel. Even though there were many submissions, none of them demonstrated access to actual customer data. Two separate flaws were found in the Linux kernel networking stack rather than Vercel's own sandbox code that were the most significant. 

Various issues can lead to memory leaks from the host kernel, while others can cause a host system crash deterministically. It is particularly relevant to cloud environments since Linux kernel isolation layers are used by many infrastructure platforms. Therefore, a vulnerability that crosses the boundary between a microVM and its host may result in consequences that extend beyond a single deployment or service. 

There were roughly two weeks before the Linux kernel maintainers were informed about the kernel issues, according to Vercel. Details remain undisclosed while fixes are in private review, with CVEs expected to be assigned after public disclosure. In addition to white-box testing, Trail of Bits engineers reported 20 findings after participating in the challenge. 

The assessment did not only identify individual vulnerabilities but also highlighted architectural concerns related to the data movement between the host control plane and the guest environment. It was recommended that all values generated within the microVM be treated as untrusted guest input. Vercel acknowledged that certain values returned by software running within a guest had been accepted by its control plane, creating an architectural risk at the boundary of the sandbox. 

AI-Assisted Triage Handles Report Surge 

A separate challenge for Vercel was also presented during the two-week program: handling the staggering number of vulnerability reports generated. When 1,285 submissions were received within a short period of time, the original review process, involving a human assessment of each report, soon became challenging to scale.

Vercel developed the Eve framework as a means of implementing an agentic triage system. Using Vercel Sandbox, the system can evaluate submitted reports against program rules, identify duplicates, access relevant source code, and execute researchers’ proof-of-concept code. This approach was implemented to alleviate the manual workload that was created by the unusually high number of submissions. 

The volume itself was partly influenced by the challenge structure, which encouraged researchers to actively seek ways to avoid the sandbox boundaries. As Vercel noted, the experience also demonstrated the effectiveness of AI-assisted security research in facilitating the discovery of new vulnerabilities more quickly. 

The white box assessment, in addition to identifying technical vulnerabilities, also revealed architectural findings concerning the trust relationship between microVM guest hosts and control planes. According to the assessment, some values returned by software running inside a microVM were accepted by the control plane.

A Vercel representative stated that such values should not be treated as trusted data, but rather as tenant-controlled inputs. This company recommends obtaining sensitive values from the server end or encrypting them with cryptographic signatures with keys that cannot be accessed from the guest environment in order to protect them. According to the company, the findings have resulted in changes to the security controls and sandbox architecture. 

While the Linux kernel issues remain under coordinated disclosure, technical details and CVE identifiers will be kept confidential until the fixes are published publicly. There was no evidence of customer data access as a result of the challenge, however, the kernel findings remain significant as the affected networking layer sits beneath isolation mechanisms in many cloud environments. 

After patches are released and technical disclosures are made, the scope of affected systems will be determined and remediation requirements will be determined for Linux-based infrastructures.