Digital Bazaar Forge up to 1.4.0 ASN.1 Encoding lib/asn1.js asn1.oidToDer input validation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.4 | $0-$5k | 0.77+ |
Summary
A vulnerability categorized as problematic has been discovered in Digital Bazaar Forge up to 1.4.0. Impacted is the function asn1.oidToDer of the file lib/asn1.js of the component ASN.1 Encoding. The manipulation results in input validation.
This vulnerability is known as CVE-2026-118775. It is possible to launch the attack remotely. No exploit is available.
It is advisable to upgrade the affected component.
Details
A vulnerability was found in Digital Bazaar Forge up to 1.4.0. It has been classified as problematic. Affected is the function asn1.oidToDer of the file lib/asn1.js of the component ASN.1 Encoding. The manipulation with an unknown input leads to a input validation vulnerability. CWE is classifying the issue as 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. This is going to have an impact on integrity. CVE summarizes:
Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript. Prior to 1.4.1, asn1.oidToDer() in lib/asn1.js did not range-check the first two arcs of an OID. An application that accepted an untrusted OID string, checked or authorized that string, and then encoded it with asn1.oidToDer() could emit DER representing a different, trusted OID from the one that was checked. DER parsing is not affected. This issue is fixed in version 1.4.1.
The advisory is available at github.com. This vulnerability is traded as CVE-2026-118775 since 10/28/2026. The exploitability is told to be easy. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. Technical details are known, but there is no available exploit.
Upgrading to version 1.4.1 eliminates this vulnerability.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.5VulDB Meta Temp Score: 4.4
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 3.7
CNA Vector (GitHub_M): 🔒
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: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Forge 1.4.1
Timeline
10/28/2026 CVE reserved10/29/2026 Advisory disclosed
10/29/2026 VulDB entry created
10/29/2026 VulDB entry last update
Sources
Advisory: github.comStatus: Confirmed
CNA: GitHub_M
CVE: CVE-2026-118775 (🔒)
GCVE (CVE): GCVE-0-2026-118775
GCVE (VulDB): GCVE-100-428730
Entry
Created: 10/29/2026 19:58Changes: 10/29/2026 19:58 (66)
Complete: 🔍
Cache ID: 216::103
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.