This update for python-M2Crypto fixes the following issues:
Security issues fixed:
- CVE-2026-109087: SSL.Checker subjectAltName hostname injection (bsc#1285047).
Non security issue fixed:
- swig 4.5.0 breaks python-M2Crypto (bsc#1275165).
Changes for python-M2Crypto:
- update to 0.51.0:
- CVE-2026-109087: SSL.Checker subjectAltName hostname
injection
(bsc#1285047, https://codefloe.com/mcepl/m2crypto/issues/409)
- Fix regex injection in TLS hostname verification (no CVE,
kindly reported by eGkritsis)
- adding the project to the Anthropic OSS Security Scanner
(https://github.com/anthropics/oss-scanner/pull/479)
- update to 0.50.0:
* switch to Codefloe
* isolate OpenSSL providers in private contexts
* disable legacy ENGINE bindings with OpenSSL 3 deprecations
* manage BIO ownership when attaching to SSL connections
* repair Windows CI pipeline and improve setup.py robustness
* record security-related behavior changes
* emit DeprecationWarning when RC4 cipher is instantiated
* disable TLSv1.0 and TLSv1.1 by default
* prevent out-of-bounds read in BN conversions
* preserve errno from gettimeofday failures
* restore timed read retries
- Update to 0.49.0:
- defer unavailable ENGINE constant lookup
- fixes problematic behaviour of pkcs11-provider
- support TLS 1.0 contexts with modern OpenSSL
- use Python 3 C APIs in handwritten SWIG code (bsc#1275165)
- feat: Add AES-GCM (AEAD) support to M2Crypto
- remove Black configuration from setup.cfg
- release X509V3 config with its context
- keep IOBuffer chains alive until destruction
- test: free low-level OpenSSL objects in leak tests
- avoid leaking X509V3 extension config
- free RSA exponent on modulus conversion failure
- free replaced EVP digest contexts
- wrap created X509 name entries with ownership
- own ASN1 values created from Python data
- own PKCS7 certificate stack copies
- release BIOs on explicit close
- Add AuthorityKeyIdentifier extension support
- Upgrade to 0.48.0:
- doc: another move ... this time to Codeberg (and communication
to Matrix)
- test(smime): parametrize test_write_pkcs7_der
- test(smime): fix test_signEncryptDecryptVerify
- fix(util): return bytes from passphrase callbacks
- fix(SSL.Checker): add IDN Chinese name
- test(ssl): add IDN certificate fixture coverage
- test(ssl): cover IDN hostname matching in Checker
- doc: update expected Name format in migration guide
- fix(smime): S/MIME signature verification for Outlook and
Thunderbird
- fix(provider): handle OSSL_STORE_INFO_PUBKEY compat. for
OpenSSL < 3.2
- fix: cast X509_dup in sk_X509_deep_copy to avoid type
mismatch
- fix(smime): remove obsolete Python pre-3.6 constructs
- ci: run on Codeberg with forgejo_runner
- doc: clarify the status of the project
- fix(provider): adjust the CI run on Gitea for the older
OpenSSL on Debian
- fix(evp): narrow digest and BIO pointers for mypy
- fix(init): acommodate modern packaging API
- doc: IRC channel is on Libera, Ergo was a wrong idea
- fix(tests): remove duplicate definition of IS_DEBIAN in
test_ssl
- fix(test_bio_ssl): fix TLS 1.3 deadlock and add socket
timeouts
- fix(test_bio_ssl): replace sys.exit() with self.fail() to
prevent test process crash
- ci: publish to PyPI with Sigstore attestations via Trusted
Publishing
- fix(authcookie): handle CookieError from Python 3.13.12+
(CVE-2026-0672)
- ci(leap): use setup.py bdist_wheel to bypass old pip PEP 517
wrapper
- fix(util): replace is_32bit with struct.calcsize and update
tests
- ci: add FreeBSD SourceHut CI build script
- fix(swig): avoid clang GNUC pragma block before _lib.h
- fix(provider): don't abuse TemporaryDirectory to be mkdtemp,
use that directly.
- fix(provider): gate provider APIs for OpenSSL 1.1.1
- feat(provider): add key generation and destruction methods
- docs(provider): add comprehensive documentation to Provider
module
- fix(provider): better exception handling
- doc: add a simple AGENTS.md
- feat(engine): add availability check, lifecycle helpers, and
safer cleanup
- doc(engine): Improve documentation and example of using
Engine module
- Upgrade to 0.47.0:
- feat: added full SWIG bindings for the ASN1_UTCTIME
- refactor(SWIG): adopt Python Buffer Protocol for
X509_NAME_ENTRY_set_data
- fix: allow 64-bit time_t on 32-bit systems in test_is32bit
- feat(provider): add initial OpenSSL providers support
- feat: stop supporting 32bit packages on Windows
- fix: improve detection of OpenSSL on Windows
- ci: run doctest
- fix: _matchIPAddress is failing
- feat: Add degenerate PKCS7 (.p7c) support
- fix(setup): add `packaging` as a requirement
- feat(asn1): introduce dedicated ASN1_UTCTIME class
- refactor(x509): CRL handling and testing
- feat: add function to provide the equivalent of `openssl
ciphers`.
- fix(X509): refactor new_extension to prevent memory
corruption
- ci: add tests showing the use of M2Crypto for STARTTLS
protocol
- doc: convert documentation to MyS
This security update for Trivy addresses multiple vulnerabilities by updating dependencies to fixed versions. It includes fixes for CVE-2026-97045, which involves missing checks during ancestor namespace transitions in golang.org/x/net/html that can cause parser differentials, and CVE-2026-116585, CVE-2026-116586, and CVE-2026-116587, which are multiple security issues in github.com/go-jose/go-jose before version 4.1.6. The update also resolves a syscall handling regression on ppc64le architectures and updates container base images.
A time-of-check to time-of-use (TOCTOU) race condition exists in the J2Store extension for Joomla versions 6.0.0 through 6.6.5. This flaw allows a logged-in customer to redeem a single-use gift voucher or coupon multiple times by initiating several checkout sessions simultaneously and confirming them before any are submitted. The issue arises because the balance and usage checks only consider orders that have progressed beyond the "New" state, enabling multiple redemptions of vouchers or coupons intended for single use.
CVE-2026-121769 is a high-severity SQL Injection vulnerability in the WP w3all phpBB integration plugin for WordPress. The flaw allows improper neutralization of special elements in SQL commands, potentially enabling an attacker with low privileges to execute unauthorized SQL queries. This affects versions from initial release up to, but not including, version 3.2.0. The vulnerability has been fixed in version 3.2.0.
A sophisticated phishing campaign targets hospitality customers by impersonating Booking.com and other hotel services with fake reservation pages. The campaign uses personalized reservation details to increase credibility and employs advanced features such as real-time card validation, interactive verification workflows, and multi-language support. It focuses particularly on Japanese hotels but is designed for global deployment. The phishing kit uses multiple backend endpoints to track victim progression and can prompt additional verification after initial card submission.
A missing authorization vulnerability exists in VideoWhisper.com 2Way VideoCalls and Random Chat webcam-2way-videochat, affecting versions up to 6.1.9. This flaw allows exploitation of incorrectly configured access control security levels, potentially enabling unauthorized access to certain functionalities. The vulnerability has a medium severity with a CVSS score of 5.3, indicating limited impact on confidentiality and no impact on integrity or availability.
JupyterLab Desktop is the cross-platform desktop application for JupyterLab. Prior to 4.6.2-1, JupyterLab Desktop for macOS declared the com.apple.security.cs.allow-dyld-environment-variables entitlement, allowing the dynamic linker to honor DYLD_INSERT_LIBRARIES despite the hardened runtime. An attacker who can already execute code as the current user can load an arbitrary dynamic library into the JupyterLab Desktop process and inherit TCC permissions previously granted to the application, including access to protected Documents, Desktop, or Downloads folders without another macOS prompt. Exploitation requires existing local code execution and prior TCC grants; it does not provide initial or remote code execution. Windows and Linux are not affected. This vulnerability is fixed in 4.6.2-1.
** UNSUPPORTED WHEN ASSIGNED ** Deserialization of an inbound SOAP fault in Apache Axis 1.x allows unauthenticated remote class instantiation. When a SOAP <Fault> carries a <detail><exceptionName> element, Axis loads the named class and, if a String <data> element is also present, instantiates it through its String constructor before checking that it is an AxisFault. Loading alone runs the class's static initializer. With a suitable class on the application's classpath this leads to remote code execution. The fault is parsed while the engine resolves the target service, before any per-service handler chain runs, so authentication handlers configured on a service do not protect against it. This affects all Apache Axis 1.x versions through 1.4.
As Axis 1 has been EOL we recommend you migrate to a different SOAP engine, such as Apache Axis 2/Java. Alternatively you could use a build of Axis with the patch from https://github.com/apache/axis-axis1-java/commit/41f3b4e8d04e310ca81f86b92630ab2c11d608bd applied. The Apache Axis project does not expect to create an Axis 1.x release fixing this problem.
A URL hosting an attacker payload related to CVE-2017-9841 was observed in the wild by OffSeq Mirage honeypot sensors on 2026-11-05. The URL was seen three times and is associated with the T1105 technique (Ingress Tool Transfer). The attacker infrastructure was identified in the United Arab Emirates (AE). This URL is used for tool download, callback, or exploitation targeting. Defenders are advised to block and monitor this URL and search their proxy, web, and WAF logs for any requests to it.
A missing authorization vulnerability in the balbooa.com Gridbox extension for Joomla allows unauthenticated attackers to delete submission or field files in versions prior to 2.20.5.0. This affects versions from 1.0.0 up to and including 2.20.4.2. The vulnerability is identified as CWE-862 and has a CVSS 4.0 base score of 6.9, indicating a medium severity level.
The PC launcher for the game "Goddess of Victory: NIKKE" was compromised via a supply chain attack involving tampered script files on the official CDN between September 27 and November 4, 2026. The altered scripts installed a remote access agent named K2F capable of executing arbitrary commands and stealing credentials from browsers, cryptocurrency wallets, and cloud services. The malware persisted by injecting a DLL into Chrome to intercept wallet recovery phrases. The initial compromise stemmed from domain hijacking of insightjs.com. The vendor detected and remediated the issue by replacing files and deploying automated detection and removal on November 5. Users who ran the Windows PC launcher during the compromise window were potentially affected.
The Drupal Commerce Escrow module before version 1.1.0 does not properly verify incoming webhook notifications from Escrow.com. This flaw allows attackers to forge payment and order status updates, potentially marking unpaid orders as paid or completed, or cancelling orders that are in progress.