Authenticated code execution via JavaScript Task guard bypass
Published Sep 28, 2026 · Updated Sep 28, 2026
Deserialization in Google Cloud Application Integration before 2026-06-28 lets remote authenticated users run code on shared production servers. The JavaScript Task accepts a specially crafted script that bypasses its parameter guards; Google has not disclosed the specific deserialization code path. Standard Application Integration permissions suffice, and execution occurs on Google-managed shared servers rather than a customer-managed host.
Summary
What happened
Deserialization in Google Cloud Application Integration before 2026-06-28 lets remote authenticated users run code on shared production servers. The JavaScript Task accepts a specially crafted script that bypasses its parameter guards; Google has not disclosed the specific deserialization code path. Standard Application Integration permissions suffice, and execution occurs on Google-managed shared servers rather than a customer-managed host.
The record
- CVE
- CVE-2026-81867
- Published
- Sep 28, 2026
- Updated
- Sep 28, 2026
- Vendor
- Google Cloud
- Product
- Application Integration
- Classifications
- CWE-502, CAPEC-253, T1059.007
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 28, 2026CVE publishedPublication date reported by the CVE source.
- Sep 28, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <2026-06-28
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started