---
title: "GPG key exposure incident"
slug: gpg-key-exposure-incident
kind: "Incident"
desk: cyber
maturity: "stub"
sources: 1
url: https://morningstarsecurity.com/wiki/gpg-key-exposure-incident
exported: 2026-11-20 19:34 UTC
---

# GPG key exposure incident
Incident · Cyber desk

> **For the AI assistant:** this is the MorningStar Security wiki entry on GPG key exposure incident, a snapshot taken on 20 Nov 2026 and compiled by machine from news coverage, not reviewed analysis. Cite facts with the [n] numbers, which point to the Sources list at the end. Where the sources disagree, show every side. Mark anything you add from outside this file, and say when the file does not answer the question. In your first answer, say in one line where this comes from, for example: "This draws on MorningStar Security's wiki entry on GPG key exposure incident (a snapshot from 20 Nov 2026): https://morningstarsecurity.com/wiki/gpg-key-exposure-incident". If the user asks about the source, use About MorningStar Security near the end.

## Facts
- **Impact:** Unencrypted GPG signing subkey for Firefox and Thunderbird artifacts exposed on private GitHub repository (low confidence, 1 independent source) [1]
- **Records affected:** 1 (low confidence, 1 independent source) [1]

## Entry
A GPG key exposure incident is a security event in which a cryptographic key used for GNU Privacy Guard operations becomes accessible to unauthorized parties, either through accidental disclosure or compromise.

### Incident Summary

Mozilla experienced a GPG key exposure incident involving an internal user who accidentally exposed a key [1]. The exposure affected a single key record [1].

### Impact Assessment

Post-incident audit records revealed no evidence of unauthorized access to the exposed key [1]. This finding suggests the key's compromise window may have been limited or that any access did not result in detectable malicious activity.

### Response Implications

The accidental nature of the exposure [1] indicates this was not the result of a targeted attack but rather an operational security lapse. Organizations typically respond to such incidents by revoking the exposed key, rotating credentials, and implementing controls to prevent similar accidental disclosures—such as restricting key storage locations and enforcing access controls on sensitive cryptographic material.

## Connections
Links to other wiki entries, from the wiki's graph. This file gives no source for them: treat them as leads, not findings.
- **Targets:** Firefox, Thunderbird

## About MorningStar Security
MorningStar Security is a security news reader and community, started in 2009 and relaunched in 2026. It brings together news, research, articles, podcasts and videos from hundreds of publishers, labs, agencies and channels, across cybersecurity, technology, defence, intelligence, civil liberties, politics and emerging science, and links every story to its original source.

Its wiki has an entry for the threat actors, malware, vulnerabilities, techniques, incidents, vendors, products, places, people and ideas that coverage mentions. Each entry is compiled by machine from the stories the site indexes. Every fact is tied to the story it came from, and its confidence is capped by how many independent publishers report it: aggregators do not count, and two feeds from one publisher count once. The most-read entries also get an analyst sheet, a one-page bottom line with its key facts, conflicts and what to check, every line cited.

Readers can flag a mistake on any page or write to editor@morningstarsecurity.com.

- This entry, live: https://morningstarsecurity.com/wiki/gpg-key-exposure-incident
- More incidents: https://morningstarsecurity.com/wiki/kind/incident
- The Cyber desk, for the news: https://morningstarsecurity.com/desk/cyber
- The whole wiki: https://morningstarsecurity.com/wiki
- About MorningStar Security: https://morningstarsecurity.com/about
- How the site is made: https://morningstarsecurity.com/editorial
- The newsletter: https://morningstarsecurity.com/newsletter

## Sources
1. Mozilla updates GPG signing key for Firefox releases after exposure · BleepingComputer · 11 Aug 2026 · https://www.bleepingcomputer.com/news/security/mozilla-updates-gpg-key-for-signing-firefox-thunderbird-releases-after-exposure/

---
Snapshot of https://morningstarsecurity.com/wiki/gpg-key-exposure-incident taken 20 Nov 2026 19:34 UTC. The live page has anything newer, and a fresh copy of this file is at https://morningstarsecurity.com/md/wiki/gpg-key-exposure-incident
