CVE-2026-15531 yashbhalgat CVE debrief

Who should care

Users of HashNeRF-pytorch, especially those handling checkpoint files, should be aware of this vulnerability. Due to the rolling release model, users should monitor updates and ensure they have the latest version. Implementing compensating controls for checkpoint file handling and monitoring for pending fixes are crucial steps.

Technical summary

The vulnerability in HashNeRF-pytorch's run_nerf.py file allows for deserialization attacks through the torch.load function when handling checkpoint files. This issue requires local access to be exploited and involves the manipulation of the ckpt_path argument. The product follows a rolling release model, meaning specific affected versions are not listed. However, a fix is pending in a pull request. Users should focus on monitoring updates and implementing compensating controls.

Defensive priority

Low priority due to CVSS score of 1.9 and local attack requirement.

Recommended defensive actions

• Inventory and monitor HashNeRF-pytorch installations for updates.
• Implement compensating controls for checkpoint file handling.
• Monitor for and apply pending fixes from the vendor.
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.
• Check relevant monitoring, detection, and logs for exposed assets that need extra review.
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.

Evidence notes

Evidence is limited. Primary records indicate a vulnerability exists but provide minimal detail. Defensive actions focus on monitoring and compensating controls due to the low CVSS score and local exploit requirement. The CVE record and NVD detail page provide the most relevant information. Additional review of the GitHub repository and issue related to CVE-2026-15531 may offer further insights.

Official resources