Skip to main content
Mallory
UnratedVulnerability

CVE-2026-109117: PSKC Signature Verification Bypass in OATH Toolkit libpskc

Updated 19 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days2 mentions · peak 2 in a dayToday
CVSS-Not scored
EPSS-30-day exploit probability
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-109117CWE-347

CVE-2026-109117 is a signature-verification bypass affecting OATH Toolkit's libpskc library and pskctool utility in versions 2.0.1 through 2.6.14 when linked against libxmlsec versions older than 1.3.3. The affected configuration can verify PSKC XML signatures using attacker-controlled key material embedded in the document's KeyInfo/KeyValue structure instead of enforcing the trusted verification key supplied by the application. Consequently, attacker-signed PSKC data containing substituted HOTP/TOTP secrets can pass signature verification. OATH Toolkit 2.6.15 prevents the bypass, including when used with older libxmlsec versions.

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 receiving application can accept substituted PSKC data as authentic despite supplying a different trusted verification certificate. This compromises the authenticity and integrity of OTP secret provisioning and can cause the application to trust attacker-selected HOTP/TOTP secrets. Practical exploitation depends on defeating independent protection of the PSKC transport. No active exploitation is known, and the upstream assessment considers practical impact unlikely. Arbitrary code execution or broad availability impact is not established.

Mitigation

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

Ensure PSKC transport independently provides authenticity, integrity, and confidentiality before data reaches libpskc or pskctool. Use authenticated, integrity-protected channels such as properly validated HTTPS or SSH, or controlled offline transfer with appropriate physical safeguards. Do not rely solely on PSKC signature verification in an affected configuration. Confidentiality is also necessary because PSKC carries symmetric OTP secrets and OATH Toolkit does not support PSKC encryption.

Remediation

Patch, then assume compromise.

Upgrade OATH Toolkit to version 2.6.15 or later and/or libxmlsec to version 1.3.3 or later. Where upgrades are impractical, apply the corresponding upstream patches. The OATH Toolkit fix restricts accepted signature key information to X509Data; libxmlsec 1.3.3 disables KeyValue and DEREncodedKeyValue nodes by default. Confirm the libxmlsec version actually linked to libpskc rather than relying solely on the installed OATH Toolkit package version.

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.
FAQ

Frequently asked questions

Is CVE-2026-109117 exploited in the wild?
As of Nov 3, 2026, Mallory has no reports of CVE-2026-109117 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-109117?
As of Nov 3, 2026, Mallory has found no public exploit for CVE-2026-109117.
Is there a patch for CVE-2026-109117?
Upgrade OATH Toolkit to version 2.6.15 or later and/or libxmlsec to version 1.3.3 or later. Where upgrades are impractical, apply the corresponding upstream patches.
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 activity3Community discussion across Reddit, Mastodon, and other social sources.