Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-112105 Overview
CVE-2026-112105 is an improper certificate validation vulnerability [CWE-287] in GlitterWare Passy, an open-source password manager, affecting versions up to 1.10.1. The flaw resides in the MyHttpOverrides class within lib/main.dart, which overrides the default badCertificateCallback to accept any TLS certificate presented by a remote host. This behavior disables certificate chain validation for HTTPS traffic initiated by the application. An attacker positioned on the network path can present a forged or self-signed certificate and the client will treat the connection as trusted. The maintainers fixed the issue in version 1.10.2 through commit 3d48df7cce05e39fa4de1e42768492307f26882e.
Critical Impact
An on-path attacker can intercept TLS traffic between Passy and remote endpoints by presenting any certificate, enabling man-in-the-middle interception of application communications.
Affected Products
- GlitterWare Passy versions up to and including 1.10.1
- Component: TLS Handler (lib/main.dart)
- Fixed in GlitterWare Passy 1.10.2
Discovery Timeline
- 2026-10-19 - CVE-2026-112105 published to NVD
- 2026-10-19 - Last updated in NVD database
- Patch commit - 3d48df7cce05e39fa4de1e42768492307f26882e merged in release v1.10.2
Technical Details for CVE-2026-112105
Vulnerability Analysis
The root issue is a deliberate override of Dart's default HTTPS trust logic. Passy extends HttpOverrides and installs a badCertificateCallback that unconditionally returns true. In Dart's dart:io HTTP stack, this callback is invoked when the presented X.509 certificate fails default validation. Returning true instructs the runtime to accept the connection regardless of the error, which effectively neutralizes TLS trust decisions for every outbound HTTPS request made through the global HttpClient.
Because Passy is a password manager, any outbound HTTPS traffic handled by this client, including synchronization or update checks, becomes susceptible to interception. The attack requires an adversary with network path control between the client and the destination server, which raises exploitation complexity but does not eliminate risk on hostile networks such as public Wi-Fi or compromised routers.
Root Cause
The root cause is an insecure global HttpOverrides implementation that bypasses certificate validation ([CWE-287: Improper Authentication / certificate validation subclass]). The callback accepts the host and port of any peer that produces an invalid certificate chain.
Attack Vector
Exploitation requires a network-adjacent attacker capable of intercepting traffic, for example through ARP spoofing, rogue Wi-Fi access points, or upstream network compromise. The attacker presents an attacker-controlled TLS certificate; the Passy client accepts it and establishes an encrypted session with the attacker rather than the legitimate server.
// Vulnerable code removed in patch 3d48df7c (lib/main.dart)
class MyHttpOverrides extends HttpOverrides {
@override
HttpClient createHttpClient(SecurityContext? context) {
return super.createHttpClient(context)
..badCertificateCallback =
(X509Certificate cert, String host, int port) => true;
}
}
Source: GitHub Commit 3d48df7c
The patch removes the MyHttpOverrides class entirely, restoring Dart's default certificate validation behavior.
Detect Identity Attacks the Moment Authentication Fails
Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.
Stop Identity AttacksDetection Methods for CVE-2026-112105
Indicators of Compromise
- Unexpected TLS handshakes from Passy clients to hosts that are not official GlitterWare or user-configured sync endpoints.
- Presence of self-signed or non-trusted root certificates in captured TLS sessions originating from Passy processes.
- Installation of Passy binaries at or below version 1.10.1 across managed endpoints.
Detection Strategies
- Inventory installed Passy versions on managed endpoints and flag any build earlier than 1.10.2.
- Inspect network telemetry for TLS sessions where the server certificate chain fails validation but the Passy client still completes the handshake.
- Review source distributions and forks for the MyHttpOverrides pattern that returns true from badCertificateCallback.
Monitoring Recommendations
- Alert on Passy processes initiating outbound HTTPS to unexpected destinations or on non-standard ports.
- Enable TLS inspection logs on perimeter devices to surface certificate validation failures that still result in established sessions.
- Track upgrade compliance toward GlitterWare Passy 1.10.2 or later across the fleet.
How to Mitigate CVE-2026-112105
Immediate Actions Required
- Upgrade GlitterWare Passy to version 1.10.2 or later on all platforms where it is deployed.
- Advise users to avoid using Passy on untrusted networks until the upgrade is applied.
- Rotate credentials that may have transited the affected client over hostile networks.
Patch Information
The fix is published in GitHub Release v1.10.2. The relevant change is commit 3d48df7cce05e39fa4de1e42768492307f26882e, which removes the MyHttpOverrides class so that Dart's default TLS validation applies to all outbound HTTPS traffic. Additional context is available in GitHub Issue #210 and the VulDB CVE-2026-112105 entry.
Workarounds
- No vendor-supplied workaround exists for versions at or below 1.10.1; upgrade is the only supported remediation.
- Restrict Passy usage to trusted networks, such as a corporate VPN tunnel, until the upgrade is applied.
- For self-built forks, remove any HttpOverrides implementation that unconditionally returns true from badCertificateCallback and rebuild from source.
# Verify installed version and upgrade source checkout to patched release
git -C Passy fetch --tags
git -C Passy checkout v1.10.2
git -C Passy log -1 --oneline 3d48df7cce05e39fa4de1e42768492307f26882e
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

