Avoid content key packet verification fallback on publicly shared nodes

F-PROTON-DRIVE-SDK-001

Public snapshot: 26 Sep 2026. Status, releases and attribution belong to each source below; none is inferred from another record.

Recorded evidence

—score not recorded

ProtonDriveApps/sdkReported fixProtonDriveApps/sdk

Avoid content key packet verification fallback on publicly shared nodes

likely fixed publicly

details

Finding IDs: F-PROTON-DRIVE-SDK-001
Status: likely fixed publicly
Reported via: security contact
Note: public Proton Drive SDK commit 451c1bf disables content-key packet verification fallback for publicly shared nodes by setting allowContentKeyPacketFallbackVerification=false in SharingPublicNodesCryptoService. mapped as a strong public fix match; no CVE/GHSA claim is made for this record.

F-PROTON-DRIVE-SDK-001: Verification failures. Public-share key-packet handling falls back after failed verification. Reviewed 24 Sep 2026. Mechanism assessed by 1seal.

Mechanism source for F-PROTON-DRIVE-SDK-001

Security area (1seal assessment): Integrity. Publicly shared nodes no longer fall back to a content-key verification path that cannot load the owner address keys. Reviewed 21 Sep 2026.

Clarify or correct this record privately. The email subject includes the finding ID. For an existing case, continue the agreed private thread. Do not post unpublished vulnerability details in public issues. Research disclosure policy.

How this page groups evidence

This identifier groups recorded evidence; it is not an additional CVE, independent-vulnerability count or guarantee of vendor confirmation. Fixed code, released versions, attribution and independent discovery are distinct claims. Absent metadata means not recorded, not disproved. Counting rules.