❌

Visualização normal

Antes de ontemStream principal
  • ✇Cybersecurity News
  • Details and PoC Code Released for Three GoAhead TLS Vulnerabilities Do Son
    FoxIO releases details and proof-of-concept code for three GoAhead TLS vulnerabilities, including a CVSS 9.1 revoked-certificate bypass. Patch to 6.1.1. Related Posts: Kerio Connect Vulnerability CVE-2026-112353 Exploited in the Wild to Steal Mailboxes Apache Kafka Fixes 12 Vulnerabilities, Including a JWT Bypass That Grants Full Cluster Access FreeSWITCH Vulnerability CVE-2026-116779 Exploited in the Wild to Run Commands The post Details and PoC Code Released for Three GoAhead TLS Vulnerabil
     

eMudhra to Exit SSL/TLS Market After 8 CA Keys Found Easily Guessable

eMudhra will leave the global SSL/TLS certificate market after eight intermediate CA private keys were found easily guessable, prompting browser distrust actions.
  • ✇Cybersecurity News
  • OpenSSL 4.1.0 Release Introduces Elbrus Support and DTLS 1.3 Do Son
    The OpenSSL 4.1.0 release introduces initial Elbrus e2k architecture support, DTLS 1.3 protocol capabilities, and post-quantum performance upgrades. Related Posts: Apple Presto Return Scanner Targets In-Box Fraud Come Back to Firefox Campaign Champions Web Privacy eMudhra Rogue Certificates Flood Certificate Transparency The post OpenSSL 4.1.0 Release Introduces Elbrus Support and DTLS 1.3 appeared first on Daily CyberSecurity.
     
  • ✇Cybersecurity News
  • wolfSSH 1.6.0 Fixes Five Flaws, Including Critical Host Key Bypass CVE-2026-16516 Do Son
    wolfSSH 1.6.0 fixes five wolfSSH vulnerabilities, including critical host key flaw CVE-2026-16516 and Windows login bug CVE-2026-83540. Related Posts: Apache DolphinScheduler 3.4.3 Fixes Six Authorization Flaws That Leak Passwords and Kubernetes Credentials Cisco Finesse SSRF Flaw CVE-2026-20362 Publicly Disclosed, With Fixes Not Due Until 2027 VMware Workstation and Fusion VMXNET3 Flaw CVE-2026-59346 Detailed With Public PoC Exploit The post wolfSSH 1.6.0 Fixes Five Flaws, Including Critical
     
  • ✇Firewall Daily – The Cyber Express
  • OpenSSL Flaw Could Expose Heap Memory and Crash Applications Ashish Khaitan
    OpenSSL has disclosed a high-severity vulnerability in its Datagram Transport Layer Security (DTLS) implementation. The flaw could let a remote peer read unintended plaintext heap memory during handshake data transmission, or cause a denial-of-service condition. Tracked as CVE-2026-84782, it stems from an out-of-bounds read in how DTLS handshake message retransmissions are handled.  According to the Security Advisory published on September 29, 2026, the bug affects OpenSSL versions 4.0, 3.6,
     

OpenSSL Flaw Could Expose Heap Memory and Crash Applications

30 de Setembro de 2026, 06:05

OpenSSL

OpenSSL has disclosed a high-severity vulnerability in its Datagram Transport Layer Security (DTLS) implementation. The flaw could let a remote peer read unintended plaintext heap memory during handshake data transmission, or cause a denial-of-service condition. Tracked as CVE-2026-84782, it stems from an out-of-bounds read in how DTLS handshake message retransmissions are handled.  According to the Security Advisory published on September 29, 2026, the bug affects OpenSSL versions 4.0, 3.6, 3.5, 3.4, 3.0, 1.1.1, and 1.0.2. 

How CVE-2026-84782 Breaks OpenSSL's DTLS Retransmission Logic 

DTLS is built for datagram-based transports, where packets can go missing, so it includes retransmission mechanisms to recover lost handshake packets. That recovery feature is where the problem lies.  The trouble starts when an application sends a DTLS handshake message in several fragments and the transport temporarily stops accepting data. OpenSSL may then return a WANT_WRITE status, pausing the handshake write partway through. While the write is suspended, a DTLS retransmission timer can expire and try to resend an earlier handshake message from the retransmission queue.  At that point, OpenSSL's retransmission code wrongly reuses the internal buffer and tracking state tied to the paused write. Instead of resetting its read position to the start of the queued message, it may begin at the offset the in-progress write had already reached.  As a result, a peer can receive a malformed or mislabeled DTLS handshake message containing leftover bytes from an unrelated, larger message still in transit. In some cases, the read extends past the intended buffer, exposing heap-resident data in plaintext. 

Memory Disclosure and Crash Risks 

The weakness is classified as CWE-125, an out-of-bounds read, and its main security impact is unintended disclosure of heap memory to the remote DTLS peer. What leaks depends on the process's memory contents and runtime conditions, and it could include fragments of previously allocated application or library data. The advisory, however, has not confirmed any reliable arbitrary-memory disclosure capability.  The bug can also crash a process if the retransmission logic reads from an unmapped memory region, creating a denial-of-service risk for applications that handle attacker-controlled DTLS traffic.  A related issue in the same retransmission path can corrupt the bookkeeping needed to resume the suspended handshake write. If a retransmission occurs while another write is still paused, later calls to SSL_read(), SSL_write(), SSL_accept(), or SSL_connect() may run into inconsistent states, triggering an abort in debugging builds. 

OpenSSL Releases Fixes for the DTLS Vulnerability 

OpenSSL fixed the problem by resetting the retransmission read position before a message is resent. The patch also skips retransmissions while a handshake write is suspended, deferring them until the application resumes the pending operation. 
Affected branch  Fixed release 
OpenSSL 4.0  4.0.3 
OpenSSL 3.6  3.6.5 
OpenSSL 3.5  3.5.9 
OpenSSL 3.4  3.4.8 
OpenSSL 3.0 Premium Support  3.0.23 
OpenSSL 1.1.1 Premium Support  1.1.1zj 
OpenSSL 1.0.2 Premium Support  1.0.2zs 
The OpenSSL FIPS module is not affected, since the vulnerable DTLS code sits outside its boundary.  Organizations are advised to identify internet-facing services, VPNs, VoIP systems, IoT deployments, and custom applications that rely on DTLS, and to promptly upgrade their bundled or system-provided OpenSSL packages.  Laurent Gaffie of SecuRizon reported CVE-2026-84782 on August 17, 2026, and Ryan Hooper developed the fix. 
  • ✇Cybersecurity News
  • Critical Python SSL Vulnerabilities Fixed in CPython Do Son
    CPython developers fixed critical Python SSL vulnerabilities. Update now to resolve these Python SSL vulnerabilities and protect secure network sockets. Related Posts: PoC Exploit Released for Next.js RCE Flaw CVE-2026-94545 ASUS Security Vulnerabilities Expose Routers and Motherboards MediaWiki External Data CVE-2026-100382 (CVSS 10) Unauthenticated RCE Exploited in the Wild, PoC Public The post Critical Python SSL Vulnerabilities Fixed in CPython appeared first on Daily CyberSecurity.
     
  • ✇Cybersecurity News
  • wolfSSL 5.9.4 Fixes 10 Vulnerabilities, Including TLS Authentication Bypass Flaws Do Son
    wolfSSL 5.9.4 patches 10 wolfSSL vulnerabilities, including TLS authentication bypass flaws CVE-2026-93302 and CVE-2026-89136. Upgrade now. Related Posts: macOS SMB Kernel Flaw CVE-2026-84543: Details and PoC Exploit Released Octopus Server Flaw CVE-2026-101169 Allows Code Execution via Insecure Deserialization Exploited Citrix NetScaler Flaw CVE-2026-88771: Details and PoC Now Public The post wolfSSL 5.9.4 Fixes 10 Vulnerabilities, Including TLS Authentication Bypass Flaws appeared first on
     
  • ✇Security Boulevard
  • DNSSEC Validation for SSL Certificates: CA/B Forum Ballot SC-085 Changes in March 2026 Janki Mehta
    Beginning March 2026, Certificate Authorities (CAs) must verify DNSSEC signatures during CAA evaluation and Domain Control Validation (DCV) if DNSSEC has been enabled on the domain. This change has been approved by the CA/Browser Forum through the CA/B Forum Ballot SC-085v2 (TLS) and SMC014 (S/MIME). With this change, DigiCert has started validating DNSSEC during theRead More The post DNSSEC Validation for SSL Certificates: CA/B Forum Ballot SC-085 Changes in March 2026 appeared first on Encrypt
     

DNSSEC Validation for SSL Certificates: CA/B Forum Ballot SC-085 Changes in March 2026

12 de Março de 2026, 06:29

Beginning March 2026, Certificate Authorities (CAs) must verify DNSSEC signatures during CAA evaluation and Domain Control Validation (DCV) if DNSSEC has been enabled on the domain. This change has been approved by the CA/Browser Forum through the CA/B Forum Ballot SC-085v2 (TLS) and SMC014 (S/MIME). With this change, DigiCert has started validating DNSSEC during theRead More

The post DNSSEC Validation for SSL Certificates: CA/B Forum Ballot SC-085 Changes in March 2026 appeared first on EncryptedFence by Certera - Web & Cyber Security Blog.

The post DNSSEC Validation for SSL Certificates: CA/B Forum Ballot SC-085 Changes in March 2026 appeared first on Security Boulevard.

❌
❌