Skip to main content
Mallory
MediumVulnerability

CVE-2018-16150: Improper Signature Verification in axTLS x509 PKCS#1 v1.5

Published Nov 7, 2018 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS5.9Medium · v3
EPSS0.59%49th percentile
CISA KEVNoNot listed
In the wildReported1 exploitation record in Mallory
Vendor
Axtls Project
IdentifiersCVE-2018-16150CWE-347 · Improper Verification of…

CVE-2018-16150 is a vulnerability in the sig_verify() function in x509.c of axTLS version 2.1.3 and earlier. The implementation of PKCS#1 v1.5 signature verification fails to reject excess data appended after the hash value in a signature. This flaw allows an attacker to forge signatures, especially when small public exponents are used, enabling the creation of fake X.509 certificates and impersonation attacks. This issue is a variant of the earlier CVE-2006-4340.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

A remote attacker can exploit this vulnerability to forge valid signatures on X.509 certificates, potentially impersonating trusted entities. This undermines the trust model of PKI, allowing man-in-the-middle attacks, spoofing, and unauthorized access to systems relying on axTLS for certificate validation.

Mitigation

If you can’t patch tonight, do this now.

If immediate upgrade is not possible, restrict the use of small public exponents in certificates and consider disabling or limiting the acceptance of untrusted certificates. Monitor for suspicious certificate activity and consider additional certificate validation checks in the application layer.

Remediation

Patch, then assume compromise.

Upgrade to a version of axTLS where the PKCS#1 v1.5 signature verification properly rejects excess data after the hash value. Ensure that the signature verification code strictly adheres to the PKCS#1 v1.5 specification and validates the entire structure of the signature.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Axtls ProjectAxtlsapplication
FAQ

Frequently asked questions

Is CVE-2018-16150 exploited in the wild?
Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2018-16150?
As of Oct 16, 2026, Mallory has found no public exploit for CVE-2018-16150.
Is there a patch for CVE-2018-16150?
Upgrade to a version of axTLS where the PKCS#1 v1.5 signature verification properly rejects excess data after the hash value. Ensure that the signature verification code strictly adheres to the PKCS#1 v1.5 specification and validates the entire structure of the signature.
What products are affected by CVE-2018-16150?
Axtls Project Axtls.
How severe is CVE-2018-16150?
CVE-2018-16150 has a CVSS v3 score of 5.9 (Medium) and an EPSS score of 0.59% (49th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.