Netflix sued over missing unreleased Nicolas Cage film
Verified Risk Digest record for Op-Fortitude Ltd. v. Netflix, Inc. (2:26-cv-08384, C.D. Cal.), the suit over the missing unreleased Nicolas Cage film: docket metadata, claims, damages theory, and a confirmed-versus-reported breakdown, sourced to the complaint PDF and PACER docket. Complaint-stage only, with no answer or ruling as of the 7/31/26 docket check.
- Jurisdiction
- United States – C.D. Cal.
- Court
- U.S. District Court for the Central District of California
- Judge
- Andre Birotte Jr.
- AI tool named
- No AI tool named
- Ruling date
- Jul 29, 2026
- Source document
- View primary court order ↗
- Last verified
- Jul 31, 2026
Lex Machina Review is an independent risk-tracking and reference resource. Nothing on this site is legal advice, and using it does not create an attorney-client relationship. Every record is reviewed against primary sources but may not reflect the most current status of a matter — always verify directly against the cited court order, rule text, or a licensed attorney before relying on it.
Companion explanation — secondary to the source document above
Record status: complaint-stage only
Risk Digest note: this record is for verification and monitoring, not legal advice. Last docket check: July 31, 2026. The Netflix lawsuit over the unreleased Nicolas Cage film is Op-Fortitude Ltd. v. Netflix, Inc., No. 2:26-cv-08384, in the U.S. District Court for the Central District of California. The case was filed on July 29, 2026, assigned to Judge Andre Birotte Jr., and referred to Magistrate Judge Steve Kim. As reflected in the docket materials checked through July 31, there was no answer, motion to dismiss, merits ruling, or adjudicated fact finding yet. [1]
That procedural status controls how the story can safely be told. This is a complaint-stage, non-AI, adjacent data-custody risk item. The reviewed record does not plead or identify an AI tool, AI output, hallucination, model vendor, AI input, training-data dispute, or sanctions issue. The professional value of the record is the custody chain around a digital film master and the parties’ competing loss-allocation positions, not the celebrity hook.

| Field | Verified record |
|---|---|
| Case | Op-Fortitude Ltd., a United Kingdom company v. Netflix, Inc., a Delaware corporation [1] |
| Docket | 2:26-cv-08384 [1] |
| Court | U.S. District Court for the Central District of California [1] |
| Filed | July 29, 2026 [1] |
| Judge / magistrate | Judge Andre Birotte Jr.; referred to Magistrate Judge Steve Kim [1] |
| Nature of suit / jurisdiction label | 190 Contract - Other; 28:1332 diversity [1] |
| Current posture | Complaint filed; no answer, motion, or ruling shown in the checked docket record through July 31, 2026 [1] |
| Risk Digest classification | Non-AI data-custody risk record; adjacent to AI-risk coverage only because it involves digital-asset custody and verification discipline |
The custody timeline that matters
The complaint does not become true because it is detailed. But it does provide a concrete sequence that can be tracked against later pleadings, declarations, discovery, or a court ruling. The sequence begins with Netflix’s alleged interest in the film in December 2025 and runs through the June 2026 delivery of the digital cinema package, the post-screening pickup or deletion requests, the theft disclosure, and the July 29 filing. [2]
Fortitude alleges that on June 15, 2026, associate producer Daniel Haido hand-delivered an unencrypted DCP of Fortitude to Netflix’s Los Angeles office. The next day, according to the complaint, Netflix screened the film. Fortitude then alleges that between June 17 and June 25 it made repeated requests for Netflix either to return the materials or confirm deletion. [2]
The record’s most important sentence is the June 25 email attributed in the complaint to Netflix Director of Original Film Sean Berney: “someone stole a good amount of drives.” That sentence is why this is more than a vague missing-movie item. It is a pleaded custody-chain disclosure tied to a sender, date, and allegedly retained physical or digital media. [2]
A careful reading still leaves open several material questions. The complaint alleges the DCP was unencrypted and that Netflix requested an unlocked delivery; Netflix disputes the plaintiff’s framing. The complaint alleges loss and exposure flowing from the disappeared drive; the current docket does not establish causation, damages, or breach. The complaint gives the reader a chain to verify. It does not supply a judgment.
| Date or period | What the current record says | Verification posture |
|---|---|---|
| December 2025 | Netflix allegedly expressed interest in the film. [2] | Plaintiff allegation |
| June 15, 2026 | Fortitude alleges an unencrypted DCP was hand-delivered to Netflix’s Los Angeles office by associate producer Daniel Haido. [2] | Plaintiff allegation; key custody fact |
| June 16, 2026 | Netflix allegedly screened the film. [2] | Plaintiff allegation |
| June 17–25, 2026 | Fortitude alleges it made pickup or deletion requests that were not resolved before the theft disclosure. [2] | Plaintiff allegation |
| June 25, 2026 | The complaint quotes Netflix’s Sean Berney as writing that “someone stole a good amount of drives.” [2] | Pivotal pleaded disclosure; not a court finding about legal responsibility |
| July 29, 2026 | Complaint filed in C.D. Cal. [1] | Docket-confirmed filing event |
| Through July 31, 2026 | No answer, motion, or ruling shown in the checked docket record. [1] | Procedural status only |
Film background, only as identification
The film is identified as Fortitude, a World War II thriller connected to Operation Fortitude and directed by Simon West, with Nicolas Cage playing Dusko Popov. Fortitude’s side has described a roughly $45 million personal investment and a development period of about seven years. [2][3]
Those details explain why the headline travels: unreleased film, recognizable actor, wartime espionage premise, allegedly missing master. They do not resolve the case. Conflicting entertainment-reporting details about broader cast lists or release prospects should be treated as secondary unless later tied to pleadings, authenticated production records, or undisputed party materials.
Claims and damages theory
Fortitude seeks $105 million from Netflix. The complaint’s theory, as reported and pleaded, centers on the alleged mishandling of an unreleased film master after delivery to Netflix, the alleged failure to return or delete the material on request, and the alleged commercial harm that followed from the drive’s disappearance. [2][3]
The damages presentation should not be flattened into “Netflix lost a $105 million movie.” Fox Business reported Fortitude’s asserted conservative revenue estimate as $112.5 million, described as 2.5 times the budget, and reported an 82% “top-two-box” test-screening score. Those figures are part of the plaintiff-side damages narrative; they are not judicial findings and do not establish market value. [4]
Netflix’s reported position is different. Netflix has characterized a reported $165 million demand from Fortitude as extortionate, and it has disputed the implication that the film was leaked or commercially compromised. [3][5]
At this stage, the damages question is best read as a pleaded valuation dispute with several unresolved inputs: what exactly was delivered, whether Netflix assumed or breached any custody obligation, what was stolen, whether any copy escaped further, whether marketability changed, and what measure of damages would apply if liability were later established.
Confirmed, alleged, reported, and still unproven
The cleanest way to brief this case is to separate the source layer before repeating the claim. That is the same docket-first discipline used in other Risk Digest monitoring records, including the Ariana Grande hacker lawsuit record, the Trump family Capital One record, and the Hearn docket verification workflow.
| Statement | Status as of the checked record | How to phrase it safely |
|---|---|---|
| A federal case exists over the missing unreleased Nicolas Cage film. | Confirmed by docket. | Op-Fortitude Ltd. sued Netflix in C.D. Cal. on July 29, 2026. [1] |
| Netflix disclosed that drives were stolen. | The complaint quotes a Netflix executive’s June 25 email saying “someone stole a good amount of drives.” | The record includes a pleaded Netflix email disclosing stolen drives; no court has assigned responsibility. [2] |
| The DCP was unencrypted. | Plaintiff allegation. | Fortitude alleges it delivered an unencrypted DCP to Netflix’s Los Angeles office. [2] |
| Netflix requested an unlocked delivery. | Plaintiff allegation that Netflix disputes. | Fortitude alleges Netflix requested an unlocked file; Netflix has not admitted the plaintiff’s liability theory. |
| The film leaked. | Unconfirmed on the current record. | Report the leak claim as unproven; Netflix has said there is no evidence the film leaked. [5] |
| Fortitude suffered $105 million in damages. | Demand and damages theory, not an adjudicated amount. | Fortitude seeks $105 million; the amount has not been accepted by a court. [2][3] |
| This is an AI incident. | Not supported by the reviewed pleadings or docket. | Do not classify it as an AI hallucination, model-output, training-data, or sanctions case. |

Why this belongs in Risk Digest despite no AI angle
The reason to track the case is not that it expands AI litigation. It does not, on the current record. The reason to track it is that digital master custody creates the same verification problem that appears in more obviously technology-driven disputes: a valuable file moves from one organization to another, the receiving party’s internal handling becomes central, and later coverage can easily outrun the pleadings.
For lawyers and risk teams, the operational questions are familiar. Was the transfer encrypted or unlocked? Who requested that format? Who accepted the drive? Where was it stored? Who had access? What return, deletion, or retention obligation existed after screening? What notice was given when the drive could not be produced? Which losses are traceable to the custody event rather than to ordinary distribution uncertainty?
Those questions may become legally important only if the case survives into adversarial motion practice, discovery, or settlement leverage. For now, the docket is thin: a filed complaint and early docket entries, without an answer or ruling. [1]
Where the record stops
As of the July 31, 2026 docket check, the case had been filed, assigned, and opened, but Netflix had not yet filed an answer or motion and the court had not ruled on liability, damages, custody obligations, leak allegations, or the parties’ competing characterizations. [1]
The Netflix/Fortitude suit is useful to monitor because it may test how a court treats digital master custody and loss allocation when an unreleased film asset disappears after delivery to a potential distributor. On the present record, it is not an AI matter and not a proven leak case.
References
- Op-Fortitude Ltd, a United Kingdom company v. Netflix, Inc., a Delaware corporation; PACER Monitor
- Op-Fortitude v. Netflix Complaint 7-29-26; U.S. District Court for the Central District of California; July 29, 2026
- Man invested $45M in a Nicolas Cage movie. It got stolen off Netflix’s desk.; Ars Technica; July 2026
- Netflix sued for $105M after Nicolas Cage WWII thriller goes missing, exposing leak risks; Fox Business
- Netflix sued for $105 million after unreleased Nicolas Cage movie stolen from desk, studio says; NBC News; Reuters
Related records
Tool profile
How Meta's AI Spending Reshapes Law Firm ProfitabilityGoverning regulation
Browse the obligations tracker →Preventive workflow
Browse verification workflows →
Report a correction or tip
Spotted an outdated figure, a misstated fact, or a ruling this case record should reflect? Public comments are disabled for this content given the professional cost of a misreported case outcome, penalty amount, or rule text — use the structured correction channel instead.
Report a correction or tip for this record →