Security readout for executives and security teams
Plain-English summary
A logged-in attacker could abuse crafted JDBC connection settings in BigQuery Data Transfer Service to run code inside a connector and gain broader privileges in the customer’s Google Cloud project. Google reports that it fixed the managed service on 1 May 2026 and that customers do not need to apply a patch.
Executive priority
Treat as a critical historical exposure requiring prompt verification, not emergency patch deployment. Confirm relevant projects received Google’s fix and review pre-patch activity where sensitive data or powerful service identities were involved. Raise incident priority if logs show unauthorized connector changes, code execution indicators, or privilege escalation.
Technical view
Improper validation of CData JDBC connection-string parameters allowed network-based, low-complexity code execution without user interaction. Exploitation required authenticated access. Successful exploitation could compromise confidentiality, integrity, and availability in both the connector container and tenant project. The affected service versions were those before 1 May 2026.
Likely exposure
Historical exposure was limited to BigQuery Data Transfer Service deployments using the vulnerable CData JDBC integration before 1 May 2026. The supplied record does not identify specific connector types, configurations, or affected customers. Current exposure should be resolved by Google’s managed-service patch.
Exploitation context
The vulnerability required an authenticated attacker able to supply crafted JDBC connection parameters. It was remotely reachable and rated CVSS 4.0 9.4. The record is not in KEV, and the supplied sources provide no evidence of active exploitation or public exploit availability.
Researcher notes
The weakness is classified as CWE-74 and concerns injection through JDBC connection-string parameters in a CData integration. The public bundle does not describe the precise parameter, runtime boundary, persistence, affected connector variants, detection indicators, or privilege-escalation mechanism. Avoid assuming exploitability outside BigQuery Data Transfer Service.
Mitigation direction
- No customer patching is required according to Google’s bulletin.
- Confirm the service-side fix applies to all relevant projects and connectors.
- Review access granted to identities that can configure JDBC-based transfers.
- Consult updated Google guidance if unusual connector activity is discovered.
Validation and detection
- Inventory projects that used affected JDBC transfers before 1 May 2026.
- Review audit logs for unexpected transfer configuration changes or privilege use.
- Verify connector and transfer administrators follow least-privilege access.
- Escalate suspicious historical activity through established incident-response procedures.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-74: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupContainer behavior lookup
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-12717 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.4 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/U:Clear
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/U:Clear——GoogleCloudVulnerability scoring details
Base CVSS 4.0 score
9.4CriticalVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/U:Clear
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://docs.cloud.google.com/support/bulletins#gcp-2026-056CVE reference, GoogleCloud
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of Special Elements in Output Used by a Downstream Component
Improper Neutralization of Special Elements in Output Used by a Downstream Component represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.