MONAI MONAILabel 0.9.7/3.0.2 PydicomReader writer.py PydicomReader._get_affine input validation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.5 | $0-$5k | 1.92+ |
Summary
A vulnerability was found in MONAI MONAILabel 0.9.7/3.0.2 and classified as critical. This affects the function PydicomReader._get_affine of the file monailabel/transform/writer.py of the component PydicomReader. Executing a manipulation can lead to input validation.
This vulnerability is handled as CVE-2026-48705. The attack can be executed remotely. There is not any exploit available.
Details
A vulnerability has been found in MONAI MONAILabel 0.9.7/3.0.2 and classified as critical. This vulnerability affects the function PydicomReader._get_affine of the file monailabel/transform/writer.py of the component PydicomReader. The manipulation with an unknown input leads to a input validation vulnerability. The CWE definition for the vulnerability is CWE-20. The product receives input or data, but it does
not validate or incorrectly validates that the input has the
properties that are required to process the data safely and
correctly. As an impact it is known to affect integrity, and availability.
This vulnerability was named CVE-2026-48705. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 10/27/2026).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Once again VulDB remains the best source for vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.5VulDB Meta Temp Score: 6.5
VulDB Base Score: 6.5
VulDB Temp Score: 6.5
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: Input validationCWE: CWE-20
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
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
10/27/2026 Advisory disclosed10/27/2026 VulDB entry created
10/27/2026 VulDB entry last update
Sources
Status: Not definedCVE: CVE-2026-48705 (🔒)
GCVE (CVE): GCVE-0-2026-48705
GCVE (VulDB): GCVE-100-427396
Entry
Created: 10/27/2026 16:12Changes: 10/27/2026 16:12 (50)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.