Japan's Digital Agency said on November 20, 2026 that files on the file-sharing service of its Government Solution Service (GSS) may have leaked. GSS is the shared IT platform used by central government ministries. According to Rescana's write-up of the announcement, the agency found that someone other than the intended recipients may have accessed shared files. Its investigation so far has confirmed access between July 30 and November 12, 2026. The agency suspended the service on November 12. It believes the files include personal information and has reported the case to Japan's Personal Information Protection Commission (PPC). It has not said how the access happened, how many files or people are affected, or what product runs the service. This is the agency's third data incident disclosed since September, and the second involving GSS. The agency has not said that it is connected to the October breach at its website vendor Studio Co.
What Happened
Rescana's account of the agency's statement gives this sequence:
- July 30 to November 12, 2026: the period in which the agency has so far confirmed access to files by someone other than the people they were shared with. The dates follow the agency's own figures on the Japanese calendar.
- November 12: the agency detected the possible unauthorised access. It suspended the file-sharing service the same day and cut its connection to the outside.
- November 20: public announcement. The agency says it is investigating with the police and outside specialists, has reported to the PPC, and has found no secondary harm, such as misuse of personal data, so far.
Agencies use the file-sharing service to send large files, such as meeting materials, to each other and to outside parties, including contractors. That means the exposure could reach well beyond government staff.
This is not the first GSS breach. On September 11, 2026, the agency disclosed a separate intrusion into GSS. Japanese tech publication Signal AI rebuilt that timeline from the agency's statement and Q&A:
- June 25: the agency detected a large volume of file access from a maintenance and operations account.
- July 9: the agency found that a third party had broken in through a VPN device vulnerability. It suspended the account and blocked outside communication.
- July 15: the agency reported the incident to the PPC.
- September 11: public disclosure, 78 days after detection.
The November incident involves a different part of GSS: the file-sharing service rather than files reached through a maintenance account. It also has a later access window. However, the newly confirmed access began on July 30, only three weeks after the agency said it had contained the September intrusion. The agency has not said whether the two incidents are related, and Rescana says it does not draw that link either. Readers should treat the question as open.
There is also a third incident, which is unrelated to GSS. On October 22, the agency disclosed that the cloud environment of Studio Co., a vendor that ran parts of its website, had been breached. Accounts of the timing differ. The Japan Times reports that the breach took place between September 30 and October 1 and that Studio confirmed it on October 13. NEXSIGHT Cyber Wire says, citing Studio, that the access ran until Studio fixed the flaw and closed the access route on October 13 and 14.
What Was Taken
November GSS file-sharing incident: the scope is unknown. The agency says the files are assumed to contain personal information. It has not published a count of files, records or affected people, or the types of data involved. Because the service carried meeting materials and files sent to contractors, both internal government documents and supplier documents could be involved. No one has confirmed what was actually copied or downloaded, as opposed to accessed.
September GSS incident, for comparison: about 246,000 personal records may have leaked, according to both Signal AI and Rescana. Rescana says about 57,000 of these relate to contractors and other people who worked with GSS agencies. Signal AI stresses that 246,000 is not a count of confirmed leaks. It is the number of records the agency could not rule out based on traces of the intrusion. The records mainly concern ministry staff and businesses involved in government work, not the general public. The Japan Times describes the leaked data as names and email addresses of government employees.
October Studio incident: the agency's own notice lists up to 13,323 inquiry-form submissions from May 2021 to March 2023, broken down as follows:
- 8,833 general opinions and requests
- 3,661 vaccination certificate app inquiries
- 462 workshop and event sign-ups
- 250 recruitment inquiries
- 117 requests to borrow the "Myna-chan" mascot costume
It also lists 35 Studio account records holding the names and email addresses of agency staff or contractors. NEXSIGHT gives the general-inquiry figure as 8,883 but the same 13,323 total. The agency's own breakdown adds up to 13,323, so the 8,833 figure is the consistent one. Media reports round the total to "more than 13,000." NEXSIGHT reports that data stored encrypted may also have been exposed, because the decryption keys were read in the same breach.
Why It Matters
A government file exchange is a valuable target. A service built to move meeting materials between ministries and their contractors collects the documents an espionage-minded attacker most wants, in one place and often in a usable state. The agency has not attributed any of these incidents to an actor or a motive.
The access window is long. Based on the agency's own dates, someone had access for at least 105 days before detection. It may have been longer, since the investigation is still running. On the same figures, the window opened while the agency was still responding to the first GSS intrusion and stayed open after that intrusion was announced. Defenders should ask whether their post-incident hunting covers neighbouring services on the same platform, not just the system that was first compromised.
Contractors carry the risk too. All three incidents expose people outside the agency: GSS contractors, file-share recipients and members of the public who used the website forms. Suppliers who exchanged files with any GSS agency between late July and mid-November should assume their documents may have been seen.
This fits a wider pattern in Japan. The same autumn saw other Japanese incidents involving third-party SaaS platforms, all unrelated to the Digital Agency:
- NTT Data said on November 2 that an attacker abused an authentication flaw to get administrator rights in Securitize Japan's SaaS service, which supported its STdirectServices digital securities platform. Data on 111 bond buyers (full contact details) and 2,678 others (kana names, purchase amounts, emails) was taken.
- Dentsu Digital confirmed on November 12 that data had leaked from its TONARIWA marketing platform. At least two client companies were affected, along with LINE integration access tokens.
In each case, a shared platform turned one compromise into exposure for many organisations.
The Attack Technique
For the November incident, the method is not known. The agency has not disclosed how the access happened, what product the file-sharing service runs on, or whether it involved stolen credentials, a software flaw, misconfigured sharing links or something else. The phrase "someone other than the legitimate share recipients" fits several of these, including leaked or guessable share links, a hijacked account, or a platform flaw. None of them has been confirmed.
The September GSS intrusion is better documented and is the closest available comparison. Signal AI reports, from the agency's Q&A, that:
- The VPN vulnerability exploited was public before the attack.
- Its initial CVSS severity rating was "Medium."
- The agency was patching faster than that rating would normally require, but the attacker got in before the fix was applied.
- The intruder then used a maintenance account to make large-scale file access. This happened even though GSS was built on a zero-trust design.
For the Studio breach, Studio says a vulnerability in part of its service was exploited, which made data in its cloud environment retrievable from outside. Studio replaced the connection keys on October 14.
What Organizations Should Do
- Treat files shared through GSS as potentially exposed. If you sent or received files through the GSS file-sharing service between July 30 and November 12, 2026, list what was exchanged. Assume any credentials, network diagrams, contract terms or personal data in those files are compromised, and rotate or reissue them.
- Watch for targeted phishing. Stolen meeting materials and contractor documents make convincing lures. Warn staff about messages that claim to come from the Digital Agency or other ministries, especially ones that refer to real projects. The agency has said it never asks for passwords or card details by email or phone.
- Patch internet-facing VPNs by exposure, not by CVSS score. The September breach came through a "Medium" VPN flaw that was known and scheduled for a fix. Rank fixes for internet-facing devices by whether they are exposed and whether the flaw is being exploited, and use temporary mitigations or take devices offline until patched.
- Hunt across the whole platform after an incident. When one service on a shared platform is breached, check the neighbouring services for unusual access too, including file shares, admin consoles and maintenance accounts. Keep monitoring for months afterwards, not just until the first fix is deployed.
- Lock down maintenance and service accounts. Limit what vendor and operations accounts can read, require strong authentication, and alert on bulk file access. Large-scale reads from a maintenance account were the September warning sign.
- Review your exposure to vendor SaaS. The Studio, Securitize Japan and TONARIWA incidents all followed the same pattern: one vendor platform exposed data from many customers. Check what data your SaaS vendors hold, delete what you no longer need (the Studio data went back to 2021), and confirm how quickly each vendor must notify you.
Sources: Possible File Leak at Japan Digital Agency's GSS File Sharing Servi... | デジタル庁で24.6万件の情報漏えい疑い――「中」評価の脆弱性が政府システムを突破した理由 Signal AI | デジタル庁の問い合わせ最大1万3323件に漏えいの可能性 — 委託先Studioのクラウド侵害、暗号化データの復号鍵も読み出される... | Digital Agency reports data breach via website vendor - The Japan T... | 【第二報】当社が提供する「TONARIWA」における不正アクセスに伴う個人情報漏えいに関するお詫びとご報告 電通デジタル | STdirectServicesのサービス停止についてのお知らせ(第2報) NTTデータグループ - NTT DATA GROUP | Studio 株式会社における不正アクセスによる個人情報の漏えいの可能性について|デジタル庁 | Digital Agency admits up to 13,000 personal records leaked in cyber...