147983 matches found
Stronger together: New Beazley collaboration enhances cyber resilience
Today’s cyberthreat landscape demands more than technical expertise: it requires a unified response team of technical responders, insurers, brokers, and legal counsel. This integrated approach is key to building long-term cyber resilience to help your organization anticipate, withstand, recover...
Stronger together: New Beazley collaboration enhances cyber resilience
Today’s cyberthreat landscape demands more than technical expertise: it requires a unified response team of technical responders, insurers, brokers, and legal counsel. This integrated approach is key to building long-term cyber resilience to help your organization anticipate, withstand, recover...
smb/server: fix possible refcount leak in smb2_sess_setup()
...
exfat: fix improper check of dentry.stream.valid_size
...
Apache HTTP Server: CGI environment variable override
...
Quadratic complexity in node ID cache clearing
...
Improper application of excluded DNS name constraints when verifying wildcard names in crypto/x509
...
be2net: pass wrb_params in case of OS2BMC
...
scsi: sg: Do not sleep in atomic context
...
Improper validation of <img> tag size in Text component parser
...
CVE-2025-61729 affecting package msft-golang for versions less than 1.24.11-1
CVE-2025-61729 affecting package msft-golang for versions less than 1.24.11-1. A patched version of the package is available...
Microsoft named a leader in the 2025 Gartner® Magic Quadrant™ for Email Security
We’re honored to share that Microsoft has been named a Leader in the 2025 Gartner® Magic Quadrant™ for Email Security. We believe this recognition highlights the value of Microsoft Defender for Office 365’s innovative capabilities in addressing today’s complex email security challenges. Protect...
XSS in Bootstrap button component
...
In Eclipse Paho Go MQTT v3.1 library (paho.mqtt.golang) versions <=1.5.0 UTF-8 encoded strings, passed into the library, may be incorrectly encoded if their length exceeds 65535 bytes. This may lead to unexpected content in packets sent to the server (for example, part of an MQTT topic may leak into the message body in a PUBLISH packet). The issue arises because the length of the data passed in was converted from an int64/int32 (depending upon CPU) to an int16 without checks for overflows. The int16 length was then written, followed by the data (e.g. topic). This meant that when the data (e.g. topic) was over 65535 bytes then the amount of data written exceeds what the length field indicates. This could lead to a corrupt packet, or mean that the excess data leaks into another field (e.g. topic leaks into message body).
...
Out-of-memory when loading Plist
...
Excessive read buffering DoS in http.client
...
Excessive resource consumption when printing error string for host certificate validation in crypto/x509
...
CVE-2025-62223
User interface ui misrepresentation of critical information in Microsoft Edge for iOS allows an unauthorized attacker to perform spoofing over a network...