Gemini Enterprise Agent Platform SDK for Python: Use of Insufficiently Random Values
CVE-2026-19407 is a high-severity use of insufficiently random values vulnerability in Gemini Enterprise Agent Platform SDK for Python from Google Cloud, with a CVSS 4.0 base score of 7.7 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, but only if a user takes part, for example by opening a link or file. The record lists version 1.165.1 as the first without the flaw, so updating Gemini Enterprise Agent Platform SDK for Python to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.67% chance of exploitation within 30 days, higher than 53% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Gemini Enterprise Agent Platform SDK for Python to 1.165.1 or a later version.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
- Because the attack needs a user to take part, warn users about unexpected links and files related to this product until it is patched.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Google Cloud | Gemini Enterprise Agent Platform SDK for Python | 1.16.0 up to, but not including, 1.165.1 | 1.165.1 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Attack requirements
- PresentThe target must be in a specific state or configuration for the attack to work.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- PassiveA user only needs to do something routine, such as viewing a page.
- Confidentiality (vulnerable system)
- HighSerious loss of confidentiality on the vulnerable system.
- Integrity (vulnerable system)
- HighSerious loss of integrity on the vulnerable system.
- Availability (vulnerable system)
- HighSerious loss of availability on the vulnerable system.
- Confidentiality (other systems)
- LowLimited loss of confidentiality on systems beyond the vulnerable one.
- Integrity (other systems)
- LowLimited loss of integrity on systems beyond the vulnerable one.
- Availability (other systems)
- LowLimited loss of availability on systems beyond the vulnerable one.
Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:H/SC:L/SI:L/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:Clear. Scored by CNA.
Official description
Bucket Squatting in Google Cloud Gemini Enterprise Agent Platform SDK for Python versions prior to 1.166.1 allows an attacker to achieve Remote Code Execution (RCE) and tenant-project token theft.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Use of Insufficiently Random Values
The product uses insufficiently random numbers or values in a security context that depends on unpredictable numbers.
How developers prevent this class of flaw
- Use a well-vetted algorithm that is currently considered to be strong by experts in the field, and select well-tested implementations with adequate length seeds. In general, if a pseudo-random number generator is not advertised as being cryptographically secure, then it is probably a statistical PRNG and should not be used in security-sensitive contexts. Pseudo-random number generators can produce predictable numbers if the generator is known and the seed can be guessed. A 256-bit seed is a good starting point for producing a random enough number.
- Consider a PRNG that re-seeds itself as needed from high quality pseudo-random output sources, such as hardware devices.
- Use products or modules that conform to FIPS 140-2 to avoid obvious entropy problems. Consult FIPS 140-2 Annex C (Approved Random Number Generators).
More Use of Insufficiently Random Values vulnerabilities (CWE-330)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
Recent Use of Insufficiently Random Values vulnerabilities
- 7.5 High severity
- 9.3 Critical severity
- 7.5 High severity
- 8.1 High severity
- 7.5 High severity
- 7.5 High severity
Spotted an error? Tell us.