How severe is GHSA-rg7c-g689-fr3x?

No CVSS score has been assigned to GHSA-rg7c-g689-fr3x yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-rg7c-g689-fr3x?

GHSA-rg7c-g689-fr3x affects the following packages: google-adk (PyPI), google-adk (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-rg7c-g689-fr3x?

Update google-adk to 1.28.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rg7c-g689-fr3x is resolved across your whole dependency graph.

How do I detect GHSA-rg7c-g689-fr3x in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for google-adk, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-rg7c-g689-fr3x if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-rg7c-g689-fr3x?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-rg7c-g689-fr3x can be triaged on real exposure rather than presence alone.

Is GHSA-rg7c-g689-fr3x actively exploited in the wild?

No public exploit code has been indexed for GHSA-rg7c-g689-fr3x yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-rg7c-g689-fr3x?

GHSA-rg7c-g689-fr3x has an EPSS (Exploit Prediction Scoring System) score of 1.8%, placing it in the 78th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-rg7c-g689-fr3x?

GHSA-rg7c-g689-fr3x is classified as Missing Authentication (CWE-306). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Is there exploit tooling available for GHSA-rg7c-g689-fr3x?

A Nuclei detection template exists for GHSA-rg7c-g689-fr3x, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was GHSA-rg7c-g689-fr3x published, and has it been updated?

GHSA-rg7c-g689-fr3x was published on April 13, 2026 and was last updated on June 29, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

Not in CISA KEV

GHSA-rg7c-g689-fr3x — google-adk

GHSA-rg7c-g689-fr3x is a Missing Authentication vulnerability in google-adk. A fix is available for google-adk — see the affected versions and patch details below.

Google Agent Development Kit (ADK) has a Code Injection and Missing Authentication vulnerability

Also known asCVE-2026-4810PYSEC-2026-344

Published

Apr 13, 2026

Updated

Jun 29, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Sep 19, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-rg7c-g689-fr3x.

EPSS Exploitation Probability

via FIRST.org ↗

1.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs78th percentile — riskier than 78% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

2 pkgs affected

🐍google-adk🐍google-adk

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

This vulnerability was patched in versions 1.28.1 and 2.0.0a2.

Customers need to redeploy the upgraded ADK to their production environments. In addition, if they are running ADK Web locally, they also need to upgrade their local instance.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`google-adk`	≥ 1.7.0&&< 1.28.1	1.28.1`pip install --upgrade 'google-adk==1.28.1'`
🐍PyPI	`google-adk`	≥ 2.0.0a1&&< 2.0.0a2	2.0.0a2`pip install --upgrade 'google-adk==2.0.0a2'`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for google-adk, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update google-adk to 1.28.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rg7c-g689-fr3x is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-rg7c-g689-fr3x can be triaged on real exposure rather than presence alone.

Tailored to GHSA-rg7c-g689-fr3x. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

How to detect GHSA-rg7c-g689-fr3x

A community-maintained Nuclei template exists for this CVE. You can scan for it directly:

nuclei -id ghsa-rg7c-g689-fr3x -u https://target

Template: Google ADK-Python - Unauthenticated Builder Endpoint
Severity: critical
Impact: Unauthenticated remote attackers can execute arbitrary code on the server, leading to full system compromise.
Remediation: Upgrade to versions 1.28.1 and 2.0.0a2 or later and redeploy to production and local environments.

Template by ProjectDiscovery nuclei-templates (dwisiswant0), MIT licensed. View the full template. Scan only systems you are authorised to test.

Frequently Asked Questions

A Code Injection and Missing Authentication vulnerability in Google Agent Development Kit (ADK) versions 1.7.0 (and 2.0.0a1) through 1.28.1 (and 2.0.0a2) on Python (OSS), Cloud Run, and GKE allows an unauthenticated remote attacker to execute arbitrary code on the server hosting the ADK instance. This vulnerability was patched in versions 1.28.1 and 2.0.0a2. Customers need to redeploy the upgraded ADK to their production environments. In addition, if they are running ADK Web locally, they also need to upgrade their local instance.

O3 Security · Impact-Aware SCA

Is GHSA-rg7c-g689-fr3x in your dependencies?

O3 Security finds GHSA-rg7c-g689-fr3x across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works