Possible File Leak at Japan Digital Agency's GSS File Sharing Service: What Government Suppliers Should Do Now

Rescana advisory card: possible leak of files on Japan Digital Agency's GSS file sharing service, access July 30 to November 12, 2026. No CVE.

Status: On November 20, 2026, at 02:59 EST, Japan's Digital Agency announced that files on the file sharing service of its Government Solution Service (GSS) may have leaked. GSS agencies use the service to exchange large files, such as meeting materials, with each other and with outside parties including contractors. On November 12 the agency detected possible access to files by someone other than the legitimate share recipients, and its investigation so far has confirmed that access between July 30 and November 12, 2026 (dates as given by the agency, Japan calendar). It suspended the service on November 12 and cut off its communication with the outside. The agency says the files are assumed to include personal information, it has reported the case to Japan's Personal Information Protection Commission (PPC), it is investigating with the police and outside specialists, and no secondary harm to personal information has been confirmed so far. It has not disclosed how the access happened, how many files or people are affected, or which product runs the service. We last checked all sources between 05:12 and 05:24 EST on November 20, 2026.

Executive Summary

This is the second GSS incident Japan's Digital Agency has disclosed in ten weeks. On September 11, 2026, it reported that an attacker had exploited a VPN device vulnerability and used a maintenance account to reach files on GSS, with about 246,000 personal records possibly leaked, including about 57,000 records about contractors and individuals who worked with GSS agencies. The November 20 announcement concerns the file sharing service and a later access window, while the September release described files on a GSS server reached through a maintenance account. The agency has not said whether the two incidents are related, and neither do we.

What matters for anyone who exchanged files with a Japanese government body:

  • The exposed asset is the content of shared files, not only a list of names. The service carried working documents between agencies and outside parties. Whatever was in those files, including designs, contract materials, meeting papers and any credentials or contact lists inside them, should be treated as possibly in someone else's hands (Rescana guidance).
  • The window is long. The agency confirms the access took place within a window of more than three months, from July 30 to November 12; it has not said whether it was continuous. The agency says it is still investigating the details of the period, so the window could change.
  • The agency's wording describes who, not how. "Someone other than the legitimate share recipients" tells you the files were reached outside their intended sharing. It does not say whether a link, an account, the service software or the underlying platform was abused. Until the agency says more, plan for every file that was on the service at any point in the window, including files uploaded before July 30 that had not yet been removed, not only files sent to you (Rescana's reading).
  • Contractors are on both sides of this. A supplier may have received files from an agency through GSS, or sent files to one. Either way, its documents and its staff contact details may be in the exposed set (Rescana's reading).

Who should act first (Rescana guidance). Companies that delivered work to a Japanese ministry or agency that uses GSS and exchanged files through its file sharing service that were still on the service at any point between July 30 and November 12, including shares created earlier; their own subcontractors; and any organization whose suppliers do government work in Japan, such as systems integrators, consultancies and research firms.

Technical Information

What the Digital Agency says, in its own terms. The November 20 release (Japanese) makes these points:

  • GSS provides a file sharing service to the government bodies that use GSS. Users share large files, such as meeting materials, with each other and with related parties outside their organization, such as contractors.
  • On November 12, 2026, the agency detected that files may have been accessed by someone other than the legitimate share recipient, and opened an investigation.
  • The investigation so far confirms that this access took place between July 30, 2026 and November 12, 2026. The details of the period are still being investigated.
  • The agency suspended the service on November 12, and right after detection it cut off communication between the service and the outside to prevent further outside access.
  • Some uploaded files may have leaked, and because those files are assumed to include personal information, the agency made the announcement and promptly reported to the PPC.
  • It is investigating with the police and with the help of outside specialist firms.
  • No secondary harm to personal information from the incident has been confirmed so far.

What the agency has not disclosed. CNET Japan notes that the agency did not disclose the number of files that may have leaked, the number of people affected or the specific method of access. Asahi Shimbun, in an expanded version of its report, describes the incident as unauthorized access to a core government network system that ran from at least July 30 to November 12. It says personal information may be included, and that the number of files and whether highly confidential internal government material was among them are "under investigation". Kyodo News reports the agency as announcing "unauthorized access by a third party" (第三者からの不正アクセス) and says the number of leaked items and the files involved are under investigation. The release does not name the file sharing product or its vendor, and none of the sources we read does. The release does not use the term "unauthorized access" (不正アクセス), which the agency used for the September incident; it describes access by parties other than the legitimate share recipients. Rescana's reading: that wording leaves open whether the access came through misdirected or reused share links, compromised accounts, a flaw in the service, or a wider intrusion. Each of those leads to different follow-up questions, which is why the supplier questions below ask about all of them.

Exploitation and attribution. No CVE has been named for this incident. None of the Digital Agency releases or press reports we read attributes the access to a named threat actor or reports a public claim of responsibility, and none reports leaked files being posted or offered for sale, as of 05:24 EST on November 20, 2026. No flaw has been named, and none of the sources reports a vulnerability write-up or proof-of-concept code published for this incident. The Digital Minister held his regular press conference on the morning of November 20, Japan time, before the release was posted; the agency has posted the video and says a summary will follow, and we will check it for new facts.

The September GSS incident, for context. Asahi's report recalls the September incident: 「GSSをめぐっては、9月にも政府職員らの個人情報約24万件が流出した可能性があると発表していた」 ("regarding GSS, the agency also announced in September that about 240,000 records on government staff and others may have leaked"; Rescana's translation). An earlier version, read at 05:24 EST, opened that sentence with 「ファイル共有サービスをめぐっては」 ("regarding the file sharing service"); Asahi changed it to GSS by 05:39 EST. The agency's own September release and Q&A describe mass access to files on a GSS server through a maintenance account and do not mention the file sharing service, and the agency has not tied the two incidents to the same service (Rescana's reading). The agency's September 11 release and its Q&A (see our September advisory) say:

  • On June 25, 2026, the agency detected access to a large number of files on a server using a maintenance and operations account.
  • On July 9, it found that a third party had entered the system through a vulnerability in a network connection device (VPN), suspended the account and cut the compromised device off from outside communication.
  • About 246,000 personal records may have leaked: about 189,000 about staff of GSS agencies and public servants who worked with them, and about 57,000 about contractors and individuals who worked on GSS agencies' business. The data includes names, email addresses, phone numbers and addresses, mostly work contacts from GSS user registration forms, and no My Number, bank account or pension numbers.
  • The vulnerability had been published before the attack and carried a medium CVSS rating, and the patch was not yet applied when it was exploited. The agency declined to name it.
  • The agency warned that the leaked data could be used for impersonation and phishing emails, and said it never asks for passwords or card details by email or phone.

Yomiuri Shimbun reported that the September intrusion had been going on since around late May, and that as of the end of July GSS was used by 23 organizations with about 154,000 users. Asahi gives the same figures as of July and names the agriculture ministry and the Cabinet Office among the users. Rescana's reading: the November access window begins three weeks after the July 9 containment of the VPN intrusion. The dates alone do not show a connection, and the agency has not drawn one; they do mean that suppliers who answered questions about GSS in September need to answer again, for a later period and for the file sharing service specifically.

Affected Product Versions

Item What is known
Affected service The file sharing service provided on GSS, the Digital Agency's common work environment for government bodies
Product and vendor Not disclosed by the agency; not named by any source we read
Users Government bodies that use GSS, and outside parties, such as contractors, that exchanged files with them through the service
Confirmed access window July 30, 2026 to November 12, 2026 (Japan dates); details still under investigation
Service status Suspended on November 12, 2026; communication with the outside cut off
Data Some uploaded files; personal information assumed to be included; counts not disclosed
CVE None named

Timeline (EST)

  • Late May 2026: start of the September GSS intrusion through a VPN device, per Yomiuri Shimbun (separate incident).
  • June 25, 2026: Digital Agency detects mass file access through a maintenance account (September incident).
  • July 9, 2026: VPN intrusion confirmed, account suspended and device cut off (September incident).
  • July 15, 2026: Digital Agency reports the September incident to the PPC, per its Q&A.
  • July 30, 2026: start of the confirmed access window on the GSS file sharing service (Japan date).
  • September 11, 2026: Digital Agency discloses the September incident (about 246,000 records).
  • November 12, 2026: possible access by parties other than the legitimate share recipients detected; service suspended and outside communication cut off (Japan date).
  • November 20, 2026, 02:59 EST: Digital Agency publishes the file sharing release in Japanese.
  • November 20, 2026, 03:55 EST and 04:11 EST: CNET Japan and Asahi Shimbun report the announcement.

How to Find Your Exposure

These steps are Rescana guidance. The agency has not published guidance for outside parties in this release.

  1. List your GSS file exchanges. Ask the teams that work with Japanese ministries and agencies whether they sent or received files through a GSS file sharing link that was still live at any point between July 30 and November 12, including shares created before July 30 that had not expired or been deleted. Search mailboxes for share notifications from those agencies from before and during that period, and ask your government counterparts which shares they sent you and when each was removed.
  2. Build the file list. For each exchange, record what the files were, which projects they belonged to, who sent them and when. Include files your subcontractors sent or received on your behalf.
  3. Classify what was inside. Mark files that contain credentials, system or network designs, source code, security assessments, pricing or bid material, personal data of your staff or customers, and contact lists.
  4. Find secrets in those files. Search the copies you hold for passwords, API keys, tokens, VPN or remote access details, and passwords for encrypted archives. Treat any secret found in a file that was on the service during the window as exposed. If archive passwords were sent through the same service or in the same exchange as the archive, treat the archive contents as readable.
  5. Check personal data obligations. If files you sent carried personal data, work out with your counsel what notice or reporting your own obligations require.

Workaround and Mitigation

What the Digital Agency has done, per its release: suspended the file sharing service on November 12, cut off its communication with the outside right after detection, reported to the PPC, and is investigating with the police and outside specialists.

What to do now (Rescana guidance):

  • Assume shared files were exposed. Do not wait for the agency to tell you whether your files were in the accessed set. Run the exposure steps above now.
  • Rotate what the files revealed. Change any password, API key, token, certificate, VPN profile or service account that appears in a file that was on the service during the window, and any account whose details could be rebuilt from those files. Revoke and reissue rather than reuse.
  • Watch for targeted phishing. Someone holding meeting materials and contact lists can write convincing emails that quote real projects, names and dates. Warn staff who work with Japanese government bodies to verify any unexpected request to download files, re-share documents, sign in again or change payment details through a known channel. The agency already warned in September that leaked GSS data could be used for impersonation emails.
  • Do not rely on a replacement share link you did not ask for. While the service is suspended, attackers may send fake GSS share notices. Confirm any new file sharing arrangement directly with your counterpart (Rescana guidance).
  • Monitor. Add alerts for your company name, project names and key staff names on paste sites and leak trackers, review sign-in logs from July 30 onward for accounts whose details appeared in shared files, and review access to systems described in those files.
  • Keep a record. Note what you checked, what you rotated and when. Your customers and auditors may ask.

Indicators of Compromise

The Digital Agency has not published any indicators of compromise for this incident: no IP addresses, domains, file hashes or account names. None of the press reports we read cites any. We will not list indicators that no primary source has published. Indicators are point in time; if the agency or the police publish any, validate them in your environment before you block on them.

Third-Party Risk (TPRM) Angle

The risk here sits with the suppliers that do government work in Japan. Systems integrators, consultancies, research and survey firms, translation and event companies and software vendors routinely receive and send meeting materials, specifications and contact lists through government file sharing (Rescana's reading). If one of them exchanged files through GSS in the window, its documents, and perhaps yours if you are its subcontractor or customer, may be exposed.

The suppliers to ask first (Rescana guidance):

  • Suppliers that deliver projects to Japanese ministries or agencies, especially those that handle your data or your staff details as part of that work.
  • Systems integrators and IT service providers that support Japanese government systems and also hold access to yours.
  • Subcontractors in a government delivery chain where you are the prime contractor or a partner.

Send these questions (Rescana guidance):

  1. Did you, or anyone working for you, send or receive files through the Digital Agency's GSS file sharing service that were still on the service at any point between July 30 and November 12, 2026, including shares created earlier? How did you check?
  2. Did any of those files contain our data, our staff's personal data, or details of systems that connect to ours?
  3. Did any of those files contain credentials, keys, VPN details or archive passwords? If so, what did you rotate, and on what date?
  4. Have you been contacted by the Digital Agency or the agency you work with about this incident, and what did they tell you about your files?
  5. Were you affected by the September 2026 GSS incident, and what did you change after it?
  6. How will you tell us if the agency later confirms that your files, or ours, were in the accessed set?

Ask for evidence, not reassurance: the list of exchanges checked, the file classification, the rotation dates, and any notice received from the agency. A supplier that cannot say whether it used the service in the window has not finished its check.

What to do internally (Rescana guidance): identify which of your suppliers work for Japanese government bodies that use GSS, send them the questions above this week, rotate anything of yours that appears in files they shared, brief the staff who work with them on targeted phishing, and track answers to closure. We will update this advisory if the Digital Agency discloses the method, the scope or the product, if it links the incident to the September intrusion, if the minister's press conference summary adds facts, or if files are reported posted or offered for sale.

Need help working out which of your suppliers exchanged files with Japanese government bodies through GSS, and what they shared? Our team can help you prioritize them and track their answers. Talk to an expert

Sources

Talk to an expert

Talk to Rescana about this advisory — or about how we help TPRM teams keep reviews moving.