Trusted Domain Project OpenDMARC up to 1.4.2 policy.c improper validation of unsafe equivalence in input
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.9 | $0-$5k | 0.92+ |
Summary
A vulnerability classified as critical has been found in Trusted Domain Project OpenDMARC up to 1.4.2. This affects an unknown part of the file policy.c of the component Domain Handler. The manipulation leads to improper validation of unsafe equivalence in input. This vulnerability is referenced as CVE-2026-101015. Remote exploitation of the attack is possible. Furthermore, an exploit is available. The vendor was contacted early about this disclosure but did not respond in any way.
Details
A vulnerability was found in Trusted Domain Project OpenDMARC up to 1.4.2. It has been rated as critical. This issue affects some unknown processing of the file policy.c of the component Domain Handler. The manipulation with an unknown input leads to a improper validation of unsafe equivalence in input vulnerability. Using CWE to declare the problem leads to CWE-1289. The product receives an input value that is used as a resource identifier or other type of reference, but it does not validate or incorrectly validates that the input is equivalent to a potentially-unsafe value. Impacted is confidentiality, integrity, and availability.
The advisory is shared at weitongli.com. The identification of this vulnerability is CVE-2026-101015. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details as well as a public exploit are known.
The exploit is available at weitongli.com. It is declared as proof-of-concept. The vendor was contacted early about this disclosure but did not respond in any way.
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 the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 6.9
VulDB Base Score: 7.3
VulDB Temp Score: 6.9
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: Improper validation of unsafe equivalence in inputCWE: CWE-1289 / CWE-20
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
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
09/27/2026 Advisory disclosed09/27/2026 VulDB entry created
09/27/2026 VulDB entry last update
Sources
Advisory: weitongli.comStatus: Confirmed
CVE: CVE-2026-101015 (🔒)
GCVE (CVE): GCVE-0-2026-101015
GCVE (VulDB): GCVE-100-410885
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 09/27/2026 13:38Changes: 09/27/2026 13:38 (56)
Complete: 🔍
Submitter: WeitongLi
Cache ID: 216::103
Submit
Accepted
- Submit #917216: The Trusted Domain Project OpenDMARC 1.4.2 Improper Authentication (by WeitongLi)
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.