OpenSSL 3.6.1 is out with fixes for multiple high-severity vulnerabilities affecting TLS, PKCS12, CMS, and certificate handling.

Posted by Timothy Legge on May 17 ======================================================================== CVE-2026-8507 CPAN Security Group ======================================================================== CVE ID: CVE-2026-8507 Distribution: Crypt-OpenSSL-PKCS12 Versions: through 1.94 MetaCPAN: https://metacpan.org/dist/Crypt-OpenSSL-PKCS12 VCS Repo:...

Wireshark 4.6.3 open-source network protocol analyzer is now available to download with various bug fixes and updated protocols.

been doing some tests after updating pfx2john.py to python3 (minor changes here https://github.com/kabutor/python/blob/master/pfx2john.py) I'll found out that if you use a generated PFX/P12 PKCS12 ...

Bug fixes: • [middleware] Sanitize replaced path in ReplacePathRegex middleware (#13466 @kevinpollet) • [acme] Bump software.sslmate.com/src/go-pkcs12 to v0.7.3 (#13477 @rtribotte)

X Certificate and Key management. Contribute to chris2511/xca development by creating an account on GitHub.

macOS に OpenSSL 3系で発行した p12 形式の証明書のインポートが失敗しました。原因を調査していると暗号化アルゴリズムが関係していそうでしたので対応を記事にしました。

This post describes CVE-2026-6837, an authenticated command-injection vulnerability in Zyxel’s PKCS#12 certificate export functionality. It details the vulnerable execution path, the root cause of the flaw, and the range of affected firmware versions. The analysis also includes the firmware-emulation methodology used during the investigation.

Crypt::OpenSSL::PKCS12 versions before 1.98 for Perl allow a NULL pointer dereference in print_attribute via a zero length BMPSTRING attribute. print_attribute() sizes the destination buffer for a BMPSTRING attribute from its declared byte length with `Renew(*attribute, length, char)`. A zero length attribute makes that a zero size reallocation, which Perl implements …

I'm using Terraform Acme provider to generate/renew certs and upload them to the Azure KV store. In the attribute section, I see an attribute * [`certificate_p12`] - The certificate, any intermediates, and the private key archived as a PFX file (PKCS12 format, generally used by Microsoft products). The data is base64 encoded (including padding), and its password is configurable via the [`certificate_p12_password`] argument. This field is empty if creating a certificate from a CSR. Is this attribute supposed to be a full chain? (as it is an archive of The certificate, any intermediates, and the private key) When I exported it to Azure KV and checked the content(.crt) it showed that it had only the issuer cert and not the intermediate certs.

This implements PKCS#12 / PFX loading for ML-KEM keys on platforms that support ML-KEM. Since MLKem and other PQC types do not derive from AsymmetricAlgorithm, an encapsulating type (pun intended),...

Wireshark 4.6.3 open-source network protocol analyzer is now available to download with various bug fixes and updated protocols.

Posted by Timothy Legge on May 17 ======================================================================== CVE-2026-8721 CPAN Security Group ======================================================================== CVE ID: CVE-2026-8721 Distribution: Crypt-OpenSSL-PKCS12 Versions: through 1.94 MetaCPAN: https://metacpan.org/dist/Crypt-OpenSSL-PKCS12 VCS Repo:...

CVE-2026-8507 is an out-of-bounds write vulnerability (CWE-787) in Crypt::OpenSSL::PKCS12 versions up to 1.94 for Perl. The flaw occurs during parsing of PKCS12 files containing a SAFEBAG attribute with an OCTET STRING or BIT STRING of size