A vulnerability in AcyMailing Joomla/WordPress extension versions 6.0.0 through 11.1.1 allows an unauthenticated attacker who knows a subscriber's email address to access that subscriber's record, including a secret key. This key enables the attacker to perform subscription management actions such as triggering GDPR data export and account deletion if those features are enabled.
A critical remote code execution (RCE) vulnerability exists in the Joomla extension jDownloads versions prior to 4.1.8. The flaw is due to insufficient validation of frontend thumbnail uploads, allowing users with upload permissions to upload executable files, leading to PHP code execution on the server.
The Symfony FrameworkBundle framework.trusted_proxies option and the HttpFoundation Request::setTrustedProxies() method trust remote clients as reverse proxies when the private_ranges shortcut is used, allowing remote attackers to spoof the client IP address, host and scheme in Symfony FrameworkBundle versions 7.1 prior to 7.4.23 and 8.x prior to 8.1.11, and HttpFoundation versions 7.2 prior to 7.4.23 and 8.x prior to 8.1.11. The private_ranges and PRIVATE_SUBNETS keywords resolved to IpUtils::PRIVATE_SUBNETS, the deny list of NoPrivateNetworkHttpClient, which lists the private and special-purpose prefixes a server must not connect to. Since the fix for CVE-2026-48736 (7.4.13 and 8.0.13), this list also covers the IPv6 prefixes that embed an IPv4 address: IPv4-mapped (::ffff:0:0/96), IPv4-compatible (::/96), 6to4 (2002::/16), Teredo (2001::/32) and NAT64 (64:ff9b::/96). The IPv4-mapped entry has been in the list since the private_ranges shortcut was introduced, in 7.1 for framework.trusted_proxies and in 7.2 for Request::setTrustedProxies(). Over-blocking is safe for a deny list, but when the same entries are used as the allow list of trusted proxies, they trust remote clients. A client whose connection arrives with such a source address is treated as a reverse proxy, and the X-Forwarded-For, X-Forwarded-Host, X-Forwarded-Proto, X-Forwarded-Port and X-Forwarded-Prefix headers it sends are honoured. For example, with Request::setTrustedProxies(['private_ranges'], ...), a request with REMOTE_ADDR set to ::ffff:203.0.113.7 and the headers X-Forwarded-For: 10.0.0.9, X-Forwarded-Host: evil.example.com and X-Forwarded-Proto: https makes getClientIp() return 10.0.0.9, getHost() return evil.example.com and isSecure() return true. Two kinds of deployments are exposed: a server listening on the IPv6 wildcard address without IPV6_V6ONLY reports every IPv4 client in the IPv4-mapped form, so every client is trusted, and a server reachable over IPv6 trusts any client sourcing from 6to4 or Teredo space, which is globally routed, whatever its listener. A spoofed client address defeats IP allow lists, rate limiting and audit logs; a spoofed host poisons the URLs written into password reset and login link e-mails and into shared caches; a spoofed scheme satisfies requires_channel: https over plain HTTP. Symfony 6.4 does not point any trusted proxy setting at IpUtils::PRIVATE_SUBNETS and is not affected by default, but an application that passes that constant to Request::setTrustedProxies() itself could be exposed in the same way on any version. This issue is fixed in 7.4.23 and 8.1.11.
Joomla Extension - jdownloads.com - Authenticated path traversal in jDownloads < 4.1.8 - A manipulated `update_file` form parameter could bypass the intended server-file selection restrictions and move files from outside the permitted selection directory or assign them to a download. This could expose file contents and remove source files from their original locations.
Joomla / WordPress Extension - acymailing.com - Open redirect on the subscription and unsubscription endpoints in AcyMailing 1.0.0 - 11.1.1 - On a default configuration, an attacker can craft a link on the affected site that redirects the visitor to an arbitrary external site, which is usable for phishing under the trusted domain.
Joomla Extension - jdownloads.com - Publishing of files without approval in jDownloads < 4.1.8 - Manipulated frontend submission parameters could bypass the intended publication and ownership rules. In particular, submissions could be published despite automatic publication being disabled, and ownership could be assigned contrary to the intended policy.
Joomla Extension - jdownloads.com - SSRF via external download URL field jDownloads < 4.1.8 - HTTP redirects when retrieving external download URLs could bypass validation of the original destination. This allowed server-side requests to internal or otherwise prohibited destinations and disclosure of their responses (SSRF).
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 the Trivy tool 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 the golang.org/x/net/html package that can cause parser differentials, and CVE-2026-116585, CVE-2026-116586, and CVE-2026-116587, which are multiple security issues in the github.com/go-jose/go-jose/v4 package before version 4.1.6. The update also includes other bug fixes and dependency bumps.
A remote code execution (RCE) vulnerability in Palo Alto Networks PAN-OS® software on Panorama enables an authenticated administrator with network access to execute arbitrary code with root privileges.
The security risk posed by this issue is significantly minimized by restricting access to the management interface to only trusted internal IP addresses according to our recommended best practice deployment guidelines https://live.paloaltonetworks.com/t5/community-blogs/tips-amp-tricks-how-to-secure-the-management-access-of-your-palo/ba-p/464431 .
Cloud NGFW, Prisma® Access, and standalone PAN-OS firewalls are not affected by this vulnerability.
Missing authorization in the JSON-RPC web services interface
of Extreme Networks Switch Engine (EXOS) allows an authenticated,
low-privileged (read-only) user to execute CLI show commands that are
restricted to that role through the command line interface. Successful
exploitation results in disclosure of sensitive information, including the
device configuration and the password hashes of local accounts. Configuration,
enable, and debug commands are not affected. Disclosed password hashes can be
attacked offline, and a weak password could lead to administrative access to
the device. This issue is fixed in Switch Engine 33.7.1-patch1-11,
33.1.100.133-patch1-9, and 32.7.4.15-patch1-11.
Extreme Networks would like to thank Toàn Lê (GitHub: https://github.com/toanln-cov) for responsibly disclosing this vulnerability and for working with our PSIRT team through coordinated disclosure.
A missing authorization vulnerability exists in E2Pdf.com e2pdf through version 1.32.65, allowing exploitation of incorrectly configured access control security levels. This flaw permits unauthorized access to functionality or data without proper permission checks. The vulnerability has a CVSS 3.1 base score of 6.5, indicating a medium severity impact primarily affecting confidentiality.
A URL associated with attacker activity was observed in the wild, linked to CVE-2021-41773 and CVE-2021-42013 vulnerabilities. The URL was seen 182 times on a single day and is related to the T1105 technique (Ingress Tool Transfer), indicating its use in attacker payload delivery or callbacks. The attacker infrastructure was identified in the US. This URL should be blocked and monitored in proxy, web, and WAF logs to detect potential exploitation attempts.
A buffer over-read vulnerability exists in the Windows COM+ Event System Service that allows an authorized local attacker to disclose information. The flaw involves reading beyond the intended buffer boundaries, potentially exposing sensitive data. The vulnerability requires low privileges and no user interaction to exploit. It has a medium severity rating with a CVSS score of 5.5. No specific affected versions or patch information is provided.
A vulnerability in the Windows COM+ Event System Service allows an authorized local attacker to elevate privileges by including functionality from an untrusted control sphere. This flaw can lead to full confidentiality, integrity, and availability compromise on the affected system.
CVE-2026-112968 is a use-after-free vulnerability in Windows COM that allows an authorized local attacker to elevate privileges. The flaw involves improper handling of memory leading to potential execution of arbitrary code with elevated privileges. The vulnerability has a high severity rating with a CVSS score of 7. Exploitation requires local access and high attack complexity, but no user interaction is needed.