ASR AI Security Radar

Back to incidents

AI security incident: PyTorch Lightning load_from_checkpoint has an insecure checkpoint deserialization (GH...

Source disclosure: May 12, 2026 | Published on Radar: October 15, 2026 | Source: GitHub Security Advisory | Classification confidence: 55%

Source disclosure is when the advisory appeared in this source (or was added to a catalog), not a confirmed date of exploitation. Radar publication is when this page became available.

This incident is part of the public archive. AI-specific signals are limited in the current source material, so source citations should be reviewed closely during triage. Review methodology.

PyTorch Lightning load from checkpoint has an insecure checkpoint deserialization PyTorch-Lightning versions 2.6.0 and earlier contain an insecure deserialization vulnerability (CWE-502) in the checkpoint loading mechanism. The LightningModule.load from checkpoint() method, which is commonly used to load saved model states, internally calls torch.

Why This Is AI-Related

This advisory is part of the public incident archive, but the current source material uses limited explicit AI terminology, so the cited sources should be reviewed carefully when judging AI relevance and exposure.

  • Explicit AI-specific signals are limited in the current source material, so use the cited advisory to validate scope during triage.

Affected Workflow

Model registries, artifact scanners, notebook workflows, and CI/CD steps that handle model files need immediate review.

Likely Attack Path

The malicious payload is embedded in model artifacts or serialized objects, then executes or bypasses scanning during load and inspection.

Impact

The advisory affects model artifacts or serialized AI assets, which can bypass inspection or execute during load and validation steps. Severity HIGH. Classification confidence 55%. Source channel GHSA.

Detection And Triage Signals

  • New or unsigned model artifacts entering the registry
  • Scanner output gaps for pickle or custom model formats
  • Unexpected code paths during model loading or validation jobs

Recommended Response

  • Inventory model artifacts, serialized objects, and scanners that touch the affected package or workflow.
  • Block untrusted model files and revalidate registry, CI, or notebook loading paths before restoring normal operation.
  • Review artifact provenance, scanner output, and recent model-ingestion activity for suspicious changes.

Compliance And Business Impact

Model artifact compromise undermines trust in the training and deployment chain and can create stealthy persistence in ML workflows.

Sources

Want alerts like this in real time?

Get notified with incident context, likely impact, and response guidance.

Get Notified

More incidents