yashbhalgat HashNeRF-pytorch up to 82885e698295982504eb6a26d060a6b2473e3706 Checkpoint File run_nerf.py torch.load ckpt_path deserialization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.8 | $0-$5k | 1.53 |
Summary
A vulnerability classified as problematic was found in yashbhalgat HashNeRF-pytorch up to 82885e698295982504eb6a26d060a6b2473e3706. This affects the function torch.load of the file run_nerf.py of the component Checkpoint File Handler. The manipulation of the argument ckpt_path results in deserialization.
This vulnerability is cataloged as CVE-2026-15531. The attack must be initiated from a local position. Furthermore, there is an exploit available.
This product operates on a rolling release basis, ensuring continuous delivery. Consequently, there are no version details for either affected or updated releases.
The pull request to fix this issue awaits acceptance.
Details
A vulnerability classified as problematic has been found in yashbhalgat HashNeRF-pytorch up to 82885e698295982504eb6a26d060a6b2473e3706. Affected is the function torch.load of the file run_nerf.py of the component Checkpoint File Handler. The manipulation of the argument ckpt_path with an unknown input leads to a deserialization vulnerability. CWE is classifying the issue as CWE-502. The product deserializes untrusted data without sufficiently verifying that the resulting data will be valid. This is going to have an impact on confidentiality, integrity, and availability.
The advisory is available at github.com. This vulnerability is traded as CVE-2026-15531. The exploitability is told to be easy. Local access is required to approach this attack. Technical details and a public exploit are known.
The exploit is shared for download at github.com. It is declared as proof-of-concept. The pull request to fix this issue awaits acceptance.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Vendor
Name
Version
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 4.8
VulDB Base Score: 5.3
VulDB Temp Score: 4.8
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: DeserializationCWE: CWE-502 / CWE-20
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
07/12/2026 Advisory disclosed07/12/2026 VulDB entry created
07/12/2026 VulDB entry last update
Sources
Product: github.comAdvisory: 49
Status: Not defined
Confirmation: 🔒
CVE: CVE-2026-15531 (🔒)
GCVE (CVE): GCVE-0-2026-15531
GCVE (VulDB): GCVE-100-377874
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 07/12/2026 18:01Changes: 07/12/2026 18:01 (61)
Complete: 🔍
Submitter: Dem0000000
Cache ID: 216::103
Submit
Accepted
- Submit #854906: Yash Bhalgat HashNeRF-pytorch Affected: repository version up to commit c49502ff492abca6243505961f1aa312 CWE-502 Deserialization of Untrusted Data (by Dem0000000)
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.