# CVE-2026-4644: Improper Authorization in Google Cloud Integration Connectors Leads to Project Takeover

> An authenticated user can escalate privileges and take over a Google Cloud Project via unauthorized service account attachment in Integration Connectors.

- **Severity:** High 8.5 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:H/SA:H/U:Clear`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Sep 2026
- **Updated:** 4 Sep 2026
- **Also known as:** GHSA-vwm5-6ggm-73px

## What is CVE-2026-4644?

CVE-2026-4644 is a high-severity missing authorization vulnerability in Google Cloud Integration Connectors, published on 4 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A Missing Authorization vulnerability in HTTP Connector in Google Cloud Integration Connectors versions prior to 2025-12-11 on Google Cloud Platform allows an authenticated user to escalate privileges and take over a Google Cloud Project using unauthorized service account attachment.

This vulnerability was patched on 11 December 2025, and no customer action is needed.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2026-4644?


## How do I fix CVE-2026-4644?

No fix has been published for CVE-2026-4644 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-4644 being exploited?

There is no known exploitation of CVE-2026-4644 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-4644 and fix it if it is affected.

What it is: CVE-2026-4644 is a high-severity missing authorization vulnerability in Google Cloud Integration Connectors, published on 4 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-4644 in the wild and no public exploit code.

Affected product: Google Cloud Integration Connectors. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-4644/ (Markdown: https://insights.sbomify.com/CVE-2026-4644/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-4644
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-4644
- OSV: https://osv.dev/vulnerability/CVE-2026-4644

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-4644/
Summaries are generated and may contain mistakes; the official description above is the record.