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

Recommended actionWithin 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Fix not verified

What, why and how

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.

What

Why

The application performs an authorisation check, but it does not correctly enforce the required permission boundary.

How

An attacker operating through a network path may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

Why

The application performs an authorisation check, but it does not correctly enforce the required permission boundary.

How

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation

Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.

No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material

Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.

None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path: a network path → Incorrect Authorization → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface: Network
Privileges required: Low: a basic authenticated account is required
User interaction: None
Attack complexity: Low: no specialised conditions are recorded
Security boundary: Not a CVSS 4.0 base metric
Weakness ? CWE means Common Weakness Enumeration: a standard category for the underlying weakness.: CWE-863 ↗
CWE-863: Incorrect Authorization. The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.
CVSS vector ? CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.: 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
Common Vulnerability Scoring System 4.0: the compact vector below is decoded into plain language.
AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.ATNoneAttack requirements: No additional deployment or execution condition is required.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.VCHighVulnerable-system confidentiality: A successful attack can cause a major loss.VINoneVulnerable-system integrity: No direct loss is represented by this metric.VANoneVulnerable-system availability: No direct loss is represented by this metric.SCHighSubsequent-system confidentiality: A successful attack can cause a major loss.SIHighSubsequent-system integrity: A successful attack can cause a major loss.SAHighSubsequent-system availability: A successful attack can cause a major loss.
Post-exploitation / living off the land: No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.

NetworkCWE-863

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

ENISA EUVD · EUVD-2026-70996Official EUVD mapping

Official EUVD record

Patch and workaround

Operational remediation based on structured source evidence.

Status ? Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.: Fix not verified
Affected: < 2025-12-11
Fixed: No fixed version is explicitly recorded in the structured CVE data.
Action: No verified patch reference is present in the current structured sources. Check the vendor advisory before making a change.
Workaround: No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.

Evidence and provenance

Published 4 Sept 2026 · Last source change 4 Sept 2026, 16:09 UTC · CWE-863 · Incorrect Authorization

CVE recordCVE.org · 5.2

CVSS sourceCNA

EPSS source

The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.

FIRST · tracked since 2026-09-05

European sourceENISA EUVD · EUVD-2026-70996

Product sourceCNA

Remediation sourceCVE/CNA references

CWE sourceCNA

NVD statusNVD awaiting enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates →

4 Sept 2026, 13:40 UTC
ENISA EUVD mappingEUVD-2026-70996 was added to the official ENISA EUVD mapping for this CVE.
Before
not recorded
After
{"euvdId":"EUVD-2026-70996"}
ENISA EUVD ↗
4 Sept 2026, 10:19 UTC
Catalogue recordCVE added to the BlackTree catalogue.
CNA ↗

2026-09-04CVE published

ENISA EUVD · EUVD-2026-70996↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗

Technical terms and abbreviations used in this report

CVE: Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS: Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS: Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE: Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA: CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP: Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD: National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT: A computer security incident response team that publishes warnings or coordinates incident response.
PoC: Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF: Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL: Living off the land: abuse of legitimate tools or system functions during an attack.

Improper Authorization in Google Cloud Integration Connectors Leads to Project Takeover

National CERT insights
?
CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

ENISA European Vulnerability Database

EUVD-2026-70996

What, why and how

Exploit reality and attack path

Official authority intelligence

Patch and workaround

Evidence and provenance

What changed after publication

Improper Authorization in Google Cloud Integration Connectors Leads to Project Takeover

National CERT insights ?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

EUVD-2026-70996

What, why and how

Exploit reality and attack path

Official authority intelligence

Patch and workaround

Evidence and provenance

National CERT insights
?
CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.