Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-79707 – Unauthenticated Arbitrary File Read (Path Traversal) – Google Agent Development Kit

Be the first to know when new zero-days emerge:

Summary

CVE-2026-79707 is a path traversal vulnerability in the builder endpoint of Google Cloud’s Agent Development Kit (ADK) for Python. An unauthenticated remote attacker can supply a crafted file_path query parameter to read arbitrary files on the host, with no authentication or user interaction required. The flaw carries a CVSS v4.0 base score of 8.7 (High).

Technical details

  • Root cause: The ADK builder endpoint accepts a file_path query parameter and uses it to read files without properly restricting the path to an intended directory (CWE-22, Improper Limitation of a Pathname to a Restricted Directory).
  • Trigger conditions: An attacker sends a crafted request to the builder endpoint with a file_path value containing directory traversal sequences, causing the server to return the contents of a file outside the intended scope.
  • Attack vector: Network-based, no privileges and no user interaction required (AV:N/AC:L/AT:N/PR:N/UI:N).
  • Impact: High-confidentiality impact — arbitrary file disclosure on the host running the affected ADK builder endpoint. No integrity or availability impact is reported (VI:N/VA:N).

Affected software

  • Google Cloud Agent Development Kit (ADK) for Python, package google-adk, versions 1.9.0 up to (but not including) 1.22.0.

Severity

  • CVSS v4.0 Base Score: 8.7 (High)
  • Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/U:Amber

Mitigation and recommended actions

  • Immediate: Upgrade google-adk to version 1.22.0 or later, which contains the fix for this path traversal issue.
  • If patching is not immediately possible: Restrict network exposure of the ADK builder endpoint (e.g., do not expose it directly to the internet, place it behind authentication or a network access control layer) until the upgrade can be applied.

How IONIX identifies potentially affected assets

IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Page title: Agent Development Kit Dev UI

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge