Skip to main content

HashNeRF-pytorch EUVDEUVD-2026-43277

| CVE-2026-15531 LOW
Deserialization of Untrusted Data (CWE-502)
2026-07-13 VulDB GHSA-9wjg-4fhr-x4rw
1.9
CVSS 4.0 · Vendor: VulDB
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Gain local low-privilege shell access
  2. Delivery
    Craft malicious pickle-embedded checkpoint file
  3. Exploit
    Place file at attacker-controlled or writable ckpt_path location
  4. Execution
    Trigger run_nerf.py execution with malicious ckpt_path
  5. Persist
    torch.load() deserializes pickle payload
  6. Impact
    Arbitrary code executes as training process owner

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A08:2025 - Software or Data Integrity Failures
ASVS 5.0
V1 - Encoding and Sanitization Safe deserialization, type allowlists
MITRE ATT&CK

2 techniques across 2 tactics: Execution, Initial Access

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires local system access and low-privileged user permissions, as confirmed by CVSS 4.0 AV:L/PR:L. The attacker must be able to supply or influence the ckpt_path argument passed to torch.load() in run_nerf.py, either by directly controlling the command-line argument, by writing a malicious file to a path the application is configured to load, or by intercepting a shared checkpoint directory. No network access, administrative privileges, or user interaction beyond triggering the training script are required. Exploitation is not possible when ckpt_path is always resolved from a write-protected, trusted-only directory inaccessible to the attacker. Systems where checkpoint loading is never performed or where weights_only=True is already enforced are not exploitable via this vector.

Impact

The CVSS 4.0 score of 4.8 (Medium) with vector AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N accurately reflects an attack constrained to local access with low-privilege requirements. No EPSS score was included in the provided intelligence, so probabilistic exploitation frequency cannot be quantified. The E:P supplemental metric confirms publicly available exploit code, which materially lowers the skill barrier for exploitation beyond what the medium CVSS score implies. The product is not listed in CISA KEV, consistent with a niche research tool unlikely to be a mass-exploitation target. The scope is non-changing (S:U / SC:N/SI:N/SA:N), meaning a successful exploit does not pivot laterally to other systems by design - impact is confined to the process owner on the vulnerable host. For ML researchers and data scientists who routinely share and load community checkpoint files, the real-world risk is practically higher than the score suggests, since the threat model of loading externally sourced checkpoints is common in this domain. The unmerged patch status increases residual exposure.

Exploit ScenarioDerived

A local attacker with low-privileged shell access on a machine running HashNeRF-pytorch crafts a .pt checkpoint file that embeds a malicious pickle payload - for example, a reverse shell or credential harvester - using publicly documented PyTorch pickle injection techniques. The attacker places the file at a path the victim user or automated training pipeline will supply as ckpt_path, then waits for run_nerf.py to be invoked; upon torch.load() deserializing the file, the payload executes in the context of the training process. A public proof-of-concept demonstrating this attack path has been disclosed via GitHub issue #49.

Monitor Track and reassess. Why: LOW severity (CVSS 0.1-3.9).
Patch available 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jul 13, 2026

Unsafe deserialization in HashNeRF-pytorch's Checkpoint File Handler allows a local low-privileged attacker to achieve arbitrary code execution by supplying a malicious file via the ckpt_path argument to torch.load() in run_nerf.py. All commits up to 82885e698295982504eb6a26d060a6b2473e3706 are affected; a fix exists as an unmerged pull request (PR #50). A public exploit has been disclosed via GitHub issue #49, though no CISA KEV listing has been identified, indicating no confirmed widespread active exploitation at time of analysis.

RemediationAI

No officially merged patch exists at time of analysis; the fix is pending as pull request PR #50 (https://github.com/yashbhalgat/HashNeRF-pytorch/pull/50), which has not yet been accepted into the main branch. Users should monitor that PR and manually apply the patch to their local installations by cherry-picking the changes from PR #50. As an immediate compensating control, modify run_nerf.py to pass weights_only=True to torch.load(), which restricts deserialization to tensor primitives and prevents arbitrary Python object execution - note that this may cause failures if checkpoints store non-tensor metadata, requiring additional code changes to re-serialize those components safely. Additionally, enforce a policy of only loading checkpoint files from trusted, write-protected sources, and restrict file system write permissions on checkpoint directories to prevent untrusted users from substituting malicious files. Reference the VulDB advisory at https://vuldb.com/cve/CVE-2026-15531 for updates.

Affected VersionsENISA

HashNeRF-pytorch 82885e698295982504eb6a26d060a6b2473e3706

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

HashNeRF-pytorch is a PyTorch-based research implementation of hash-encoding Neural Radiance Fields (NeRF). The vulnerability resides in run_nerf.py within the Checkpoint File Handler, which invokes Python's torch.load() to restore model state from disk. By default, torch.load() relies on Python's pickle module for deserialization, a known dangerous pattern classified under CWE-502 (Deserialization of Untrusted Data). When no weights_only=True restriction is enforced, any serialized Python object - including one embedding malicious __reduce__ hooks - can execute arbitrary code at load time. The CPE cpe:2.3:a:yashbhalgat:hashnerf-pytorch:*:*:*:*:*:*:*:* covers all releases of the project, consistent with its rolling release model and lack of versioned tags.

Know when Checkpoint gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (VulDB) PRIMARY 1.9 MEDIUM
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P
vuln.today AI 5.3 MEDIUM

Local-only exploitation via file path argument control with low privilege; no scope change and symmetric low C/I/A impact confined to the training process.

3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
4.0 AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N

Primary rating from Vendor (VulDB).

CVSS VectorVendor: VulDB

Attack Vector
Local
Attack Complexity
Low
Attack Requirements
None
Privileges Required
Low
User Interaction
None
Vulnerable system: Confidentiality
Low
Vulnerable system: Integrity
Low
Vulnerable system: Availability
Low
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

2
Severity Changed
Jul 13, 2026 - 06:22 NVD
MEDIUM LOW
CVSS changed
Jul 13, 2026 - 06:22 NVD
4.8 (MEDIUM) 1.9 (LOW)

DescriptionCVE.org

A vulnerability has been found in yashbhalgat HashNeRF-pytorch up to 82885e698295982504eb6a26d060a6b2473e3706. Affected by this issue is the function torch.load of the file run_nerf.py of the component Checkpoint File Handler. The manipulation of the argument ckpt_path leads to deserialization. The attack must be carried out locally. The exploit has been disclosed to the public and may be used. This product uses a rolling release model to deliver continuous updates. As a result, specific version information for affected or updated releases is not available. The pull request to fix this issue awaits acceptance.

Threat Intelligence Overview

EPSS Score
0.1%
Top 98% exploitable
Prevalence
Rare
niche academic NeRF research project, negligible enterprise production footprint
Exploit
POC
Public exploit code exists
Data Quality
7 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment GitHub VulDB

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity LOW
CISA KEV No
Public POC Yes
EPSS 0.1%
Patch available Yes
Active threat No
Deciding rule
LOW severity (CVSS 0.1-3.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Defer
Exploitation
Poc
System Exposure· derived
Small
Automatable
No
Human Impact· derived
Low
Technical Impact
Partial

Priority Score

30
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +10
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Insecure deserialization occurs when an application converts serialized data (a stream of bytes representing an object's state) back into a living object without proper validation.

CVE-2014-6271 CRITICAL POC
9.8 Sep 24

GNU Bash through 4.3 processes trailing strings after function definitions in the values of environment variables, which

CVE-2024-24919 HIGH POC
8.6 May 28

Potentially allowing an attacker to read certain information on Check Point Security Gateways once connected to the inte

CVE-2014-7169 CRITICAL POC
9.8 Sep 25

GNU Bash through 4.3 bash43-025 processes trailing strings after certain malformed function definitions in the values of

CVE-2017-1000083 HIGH POC
7.8 Sep 05

backend/comics/comics-document.c (aka the comic book backend) in GNOME Evince before 3.24.1 allows remote attackers to e

CVE-2026-85102 CRITICAL POC
9.8 Sep 09

Remote code execution in Check Point Quantum Security Gateway arises from improper certificate trust validation during V

CVE-2026-16232 CRITICAL POC
9.3 Jul 22

Authentication bypass in the Check Point SmartConsole login process lets an unauthenticated remote attacker mint a valid

CVE-2026-50751 CRITICAL POC
9.3 Jun 08

Authentication bypass in Check Point Quantum Security Gateway and Spark Firewalls allows unauthenticated remote attacker

CVE-2026-93616 CRITICAL POC
9.8 Sep 22

Unauthenticated attackers who can reach the file-upload interface of Check Point Management Server can combine directory

CVE-2021-3449 MEDIUM
5.9 Mar 25

An OpenSSL TLS server may crash if sent a maliciously crafted renegotiation ClientHello message from a client. Rated med

CVE-2026-85103 CRITICAL POC
9.8 Sep 09

Remote code execution in Check Point Quantum Security Gateway and Quantum Security Management stems from a heap-based bu

CVE-2026-91843 CRITICAL POC
9.8 Sep 16

Unauthenticated remote code execution affects Check Point Quantum Security Management, where a stack-based buffer overfl

CVE-2024-3568 CRITICAL POC
9.6 Apr 10

The huggingface/transformers library is vulnerable to arbitrary code execution through deserialization of untrusted data

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy