The Nikon Z6 III Incident: What Camera Signing Vulnerabilities Teach Us
What Happened
In September 2025, a forum member known as Horshack discovered a significant vulnerability in the Nikon Z6 III's C2PA implementation. Using the camera's multiple exposure overlay feature, Horshack was able to import an AI-generated image — a pug flying an airplane — encoded as a Nikon NEF file and have the camera cryptographically sign it as authentic.
The signed image passed C2PA validation. A wholly fabricated image now carried a legitimate cryptographic signature from a real camera.
Nikon suspended the Authenticity Service on September 5, 2025, and subsequently revoked all C2PA certificates issued since launch.
Why It Matters
The Nikon incident is not just a single bug — it illustrates a fundamental challenge in hardware-based content signing. When a camera signs an image, it is asserting: "This content was captured by this device." But if the device's firmware allows external content to enter the signing pipeline, that assertion is false.
As PetaPixel noted, "Nikon can't fully solve the Z6 III's C2PA problems alone." The vulnerability highlighted systemic challenges in hardware key management within signing pipelines.
The Broader Lesson
Hardware signing is necessary but not sufficient. A device-level signature proves which device produced the signature — not that the content was genuinely captured by that device's sensor. Every input path, every firmware feature, and every compositing mode becomes an attack surface.
This is exactly why sig-share's approach layers transparency logging on top of device signatures. Even if a device signature is valid, the transparency log provides an independent, auditable record. Anomalies — like a device that suddenly produces content with unusual characteristics — become detectable through log analysis rather than relying solely on the device's own assertions.
Contrast with Pixel 10
Google took a different approach with the Pixel 10, which signs every photo by default using hardware-backed keys in the Titan M2 security chip. The Pixel Camera app achieved Assurance Level 2 — the highest security rating in the C2PA Conformance Program, and the first device to do so.
But even this approach has drawn criticism from security researchers. Issues include unprotected EXIF metadata that can be altered without invalidating the signature, per-picture certificates that complicate device-level revocation, and privacy concerns about the phone querying Google for each signing event.
What This Means for sig-share
The camera signing incidents reinforce the case for open, multi-layer verification:
- Device signatures are one layer, not the whole story. They should be combined with transparency logging and independent verification.
- Open standards enable open scrutiny. The Nikon vulnerability was found by an independent researcher precisely because the system was visible enough to examine.
- Privacy and security must be designed together. Signing systems that leak metadata or require phone-home checks create new risks even as they solve old ones.
sig-share's architecture — keyless signing, transparency logs, and open verification — is designed to provide defense in depth. No single layer needs to be perfect when the system as a whole is auditable.