Cases › leaked private data › LR-2026-0050
Zhipu ZCode repository snapshot upload without clear consent
Whose AI: Z.ai (Zhipu AI) · ZCodeleaked private data
Severity moderate: Project data could be uploaded to a cloud server without clear consent, touching data of users with a bounded scope stated.
Earliest source we hold 2026-09-20
Zhipu's ZCode AI coding tool could upload project data to a cloud server without clear consent, prompting user concerns; Zhipu completed a security overhaul, and version 3.14.0 removed the RepoWiki feature and the paths used to generate and upload local repository snapshots.
Risk grouping: Not yet classified
| Who caused it | Something else “ZCode version 3.14.0 removed the RepoWiki feature and the paths used to generate and upload local repository snapshots, while the source code has […]” source |
|---|---|
| Before or after release | After release “Zhipu said it has completed a security overhaul of its ZCode AI coding tool after users raised concerns that the software could upload project data to a cloud server without clear consent.” source |
| The AI's part | Caused it “The issue came to light on Friday when an independent Chinese technical blogger known as Ferstar inspected a local directory in ZCode and found that a compressed file of 313 megabytes was pending upload to Alibaba Group Holding’s cloud storage service after failing 564 times, while a smaller 15-kilobyte file had been successfully sent.” source |
No source we hold states: intended or not.
The story
1 · What it was doingZhipu's ZCode AI coding tool was used by developers on their local projects, with the ability to generate and upload local repository snapshots to a cloud server.
2 · What went wrongThe tool could upload project data to a cloud server without clear consent, breaching users' expectation of consent over their project data.
3 · What it reached or didLocal repository snapshots and project data could reach a cloud server; the sources do not state how many users or repositories were affected.
4 · How it was caughtUsers raised concerns about the upload behaviour; the sources do not name a monitor or other first detector.
5 · What was doneZhipu completed a security overhaul; version 3.14.0 removed the RepoWiki feature and the paths used to generate and upload local repository snapshots.
No source states: {'q': 'intent', 'value': None, 'quote': None, 'url': None}.
Show every field, with its source and grade
The AI system
Model
ZCode
C one secondary source states it
Model version
3.14.0
C one secondary source states it
Developer
Z.ai (Zhipu AI)
C one secondary source states it
Whose system
company using AI
D inferred by us from the described behaviour, reason shown
How it was connected
embedded
D inferred by us from the described behaviour, reason shown
What it was for
AI coding tool
C one secondary source states it
What happened
Earliest source we hold
2026-09-20
A the date the source itself carries
What was done
ZCode version 3.14.0 removed the RepoWiki feature and the paths used to generate and upload local repository snapshots
C one secondary source states it
What went wrong
leaked private data
D inferred by us from the described behaviour, reason shown
AI agent
no AI agent acted
D inferred by us from the described behaviour, reason shown
Impact
Severity
moderate
D inferred by us from the described behaviour, reason shown
Who was affected
a commercial project he was working on, including the project’s Git history
C one secondary source states it
Kinds of data exposed
private repositories
D inferred by us from the described behaviour, reason shown
Why this severity
Project data could be uploaded to a cloud server without clear consent, touching data of users with a bounded scope stated.
D inferred by us from the described behaviour, reason shown
LR-2026-0050 · version 9 · published 2026-10-25 after automatic checks; not yet checked field by field by a person · changes to this case · JSON