Search/openssl
Vendor

openssl

Known CVEs
0
Highest CVSS
In KEV
0
Vendor
fips object module
Connections
56 relationships
わずか11バイトでメモリを圧迫 OpenSSLを狙う新DoS攻撃、その意外な仕組み
OpenSSL�ŁA���ʂ̒ʐM�ŃT�[�o�̃��������������V����DoS��肪���������B�����́ATLS�ʐM���n�܂�O�̏��������p���A��ʓI�Ȑڑ������������ł͏\���ɖh���Ȃ��\�������邱�Ƃ��B�����̃\�t�g�E�F�A�����p���郉�C�u�����[�ʼn����N���Ă����̂��B ���̋L���͉������ł��B����o�^�i�����j����ƑS�Ă������������܂��B �@Okta��2026�N7��16���i���n���ԁj�A���Ђ̃��b�h��[�����Í��ʐM���C�u�����[�uOpenSSL�v��DoS�U���������N�����Ǝ�i�������Ⴍ�j���uHollowByte�v�������ƌ��\�����B �@���u�̖��F���[�U�[�́A�킸��11�o�C�g�̍H�����f�[�^�𑗂邾���ŁA�T�[�o�ɍő��131KB�̃��������m�ۂ�������BTLS�n���h�V�F�C�N���n�܂�O�̏��������p���邽�ߔF�͕s�v�ŁA�ڑ���ؒf��������������g�p�ʂ̑������c��ꍇ������Ƃ����B �@TLS�n���h�V�F�C�N�ł́A�uClientHello�v���b�Z�[�W�̐擪4�o�C�g�ɁA�㑱����{���̒������L�^����Ă���B���ł�OpenSSL�́A���̒���������ɁA�{�����͂��O�����M�p�o�b�t�@�[���m�ۂ���d�l�������B �@�H����11�o�C�g�̃f�[�^����M����ƁAOpenSSL�̓w�b�_�ɋL�ڂ��ꂽ�T�C�Y��M�����A�ő��131KB�̃��������m�ۂ���B���������̎��_�ł͖{���͂܂��͂��Ă��炸�A���̓��e���m�F����Ă��Ȃ��B�{�������M����Ȃ���A�T�[�o�͕s�v�ȃ�������ێ������܂ܑҋ@��������B �@����ɐڑ��I����́AOpenSSL����������������Ă��A�uGNU C Library�v�iglibc�j�͍ė��p�̂��߂ɗ̈��ێ�����B���̏�ԂňقȂ�T�C�Y�̐ڑ����J��Ԃ��ƃq�[�v�̒f�Љ����i�݁A�v���Z�X�����ۂɎg�p���镨���������ʂ͑���������B�������g�p�ʂ͐ڑ��I����������ɂ͌��ɖ߂炸�A�v���Z�X�̍ċN�����K�v�ɂȂ�ꍇ������B �@Okta�̃��b�h��[���͖��C���łƏC���ł�OpenSSL��g�ݍ��uNGINX�v�Ō������{�����B������1GB�̊��ł́A���C���ł̃T�[�o����547MB�̃�������ێ������܂܂ƂȂ�A�ŏI�I��OOM�L���[�ɂ���Ē�~�����B �@������16GB�̊��ł́A�ڑ����̏���ɒB���Ȃ������ł��A�V�X�e���S�̖̂�25���̃������𗘗p�ł��Ȃ���Ԃɂł����B�ڑ����Ԉێ����ăT�[�o�������������_�́AHTTP���N�G�X�g�����������M���Đڑ��g���L����DoS�U���̈��A�X���[�����X�Ǝ��Ă���B����AHollowByte�̓������Ǘ��̎d�g�݂����p���邽�߁A�ڑ��I������������g�p�ʂ����ɖ߂�ɂ����_���������B �@�e������\��������̂́A�uApache HTTP Server�v��NGINX�Ȃǂ�Web�T�[�o�A�uNode.js�v�uPython�v�uRuby�v�uPHP�v�Ȃǂ̃����^�C���A�uMySQL�v�uPostgreSQL�v�ȂǁAOpenSSL�𗘗p����\�t�g�E�F�A���B �@�C����OpenSSL 4.0.1�̑��A3.6.3�A3.5.7�A3.4.6�A3.0.21�ɂ��o�b�N�|�[�g���ꂽ�BOpenSSL�͂��̖���CVE�t���̐Ǝ㐫�ł͂Ȃ��A���S�i����낤�j�������߂�C���Ƃ��Ĉ����Ă���BOkta Red Team�́A���p���̃f�B�X�g���r���[�V����������OpenSSL�p�b�P�[�W�֑��₩�ɍX�V����悤�Ăъ|���Ă���B Copyright © ITmedia, Inc. All Rights Reserved.
atmarkit.itmedia.co.jpJul 21, 2026extracted
OpenSSL Silently Fixes ‘HollowByte’ DoS Vulnerability
A vulnerability in OpenSSL could allow attackers to cause a server’s memory to be exhausted before any security handshake, Okta’s red team discovered. Referred to as HollowByte, the denial-of-service (DoS) bug could be triggered via a malicious payload of only 11 bytes that declares a larger incoming message body to trigger a buffer pre-allocation that is not immediately freed. HollowByte existed because older OpenSSL iterations pre-allocated receive buffer sizes based on the incoming message body length declared in the handshake message’s 4-byte header. The pre-allocation occurred before any data arrived, and an attacker could send an 11-byte payload to trigger an unvalidated buffer allocation of up to 131 KB. “The worker thread then blocks, waiting indefinitely for data that will never arrive,” Okta explains. Additionally, because the GNU C Library (glibc) retains small-to-medium memory allocations for potential reuse and does not immediately return them to the OS when a connection drops, although OpenSSL frees the buffer, multiple successive payloads could be sent to exhaust the server’s memory. “By launching waves of connections with randomized claimed sizes, an attacker prevents the allocator from reusing those freed chunks,” Okta explains. “Even after the attacker disconnects, the server remains permanently bloated. The only way to reclaim that memory is to terminate the process,” it adds. In real-world testing, a 1 GB RAM system became unresponsive after 547 MB of memory was fragmented and frozen. On a 16 GB RAM system, “the attack successfully locked up 25% of the system’s total memory while staying safely under the connection ceiling, meaning standard connection-limiting defenses won’t stop it,” Okta says. Apache, NGINX, Node.js, Python, Ruby, PHP, MySQL, PostgreSQL, and other types of applications, servers, runtimes, and databases that use OpenSSL are impacted unless they upgrade to a patched version of the open source library. Patches for HollowByte were silently included in OpenSSL version 4.0.1 and silently backported to versions 3.6.3, 3.5.7, 3.4.6, and 3.0.21. Now, the library increases the buffer size as bytes actually land and no longer trusts the handshake header for buffer growth. Related: Chrome 150 Update Patches Severe Memory Safety Bugs Related: Nightmare Eclipse Drops ‘LegacyHive’ Windows Zero-Day Related: Vulnerabilities Patched by Fortinet, Ivanti, ServiceNow Related: SonicWall Issues Urgent SMA Patch Warning for Two Zero-Day Exploits
securityweek.comJul 20, 2026extracted
Meet Dusseldorf, Microsoft’s open-source out-of-band security platform
Meet Dusseldorf, Microsoft’s open-source out-of-band security platform Out-of-band vulnerabilities surface when an application quietly reaches out to an external system during an attack, and capturing that traffic calls for infrastructure that many researchers assemble on their own. A new open-source project from Microsoft supplies that infrastructure in a package meant to run inside a private environment. Dusseldorf is an out-of-band application security testing platform. It captures inbound network traffic across several protocols and lets an operator craft automated responses for validation workflows. The name comes from a Microsoft habit of using place names for projects. The German city Düsseldorf carries the letters SSRF, and the umlaut gives way to a plain u for everyday use. The tool targets a set of defects that leave few traces inside an application. These include server-side request forgery, cross-site scripting, server-side template injection, XML external entity flaws, and related classes. Detection depends on watching what an application does at the network edge, which is where Dusseldorf sits. Once deployed, the platform runs DNS, HTTP, and HTTPS listeners tied to a domain such as *.yourdomain.net. Every request to that domain and any subdomain lands in the capture log. The project calls these subdomains zones, so foo.yourdomain.net and foo.bar.yourdomain.net both register as distinct entries. A protected graphical interface and a matching REST API give an operator a view of captured requests and their responses, along with controls for custom responses and filters. Private deployment is the design premise. An operator controls identity integration, the infrastructure footprint, the domains in play, and the runtime policies that govern request handling. Rules and service-level changes adjust how the platform answers incoming traffic. Running Dusseldorf calls for a machine on the internet with one or more public IPv4 addresses and a domain whose name server record points at those addresses. The codebase is built for Azure and splits into two deployment paths. A local path covers lab setups and developer iteration, with credential generation, certificate setup, and Docker Compose workflows. An Azure path handles cloud provisioning and database initialization through Helm. The prerequisite list reflects that dual approach. An installer needs Docker, Docker Compose, the Azure CLI, OpenSSL for TLS certificates, Python 3 with pip, the jq utility, and Helm. After deployment, operators work through the interface and API, with a command-line path documented alongside them. Dusseldorf is available for free on GitHub. Must read: 20 open-source cybersecurity tools to keep your team ready for anything GitHub CISO on security strategy and collaborating with the open-source community Subscribe to the Help Net Security ad-free monthly newsletter to stay informed on the essential open-source cybersecurity tools. Subscribe here!
helpnetsecurity.comJul 20, 2026extracted
OpenSSL HollowByte Flaw Could Freeze Server Memory with 11-Byte TLS Requests
Eleven bytes will make an unpatched OpenSSL server set aside up to 131 KB of memory for a message that never arrives. On the glibc systems Okta tested, that memory is gone until the process restarts. OpenSSL shipped the HollowByte fix in June with no CVE, no advisory, and no changelog entry pointing at it. Okta's Red Team, which reported the denial-of-service bug and named it, published the details on Thursday. The fixed releases are OpenSSL 4.0.1, 3.6.3, 3.5.7, 3.4.6, and 3.0.21, all dated June 9. Every release on those branches before the fixed ones has it. Nothing in a normal patch pipeline will point you at them: there is no identifier for a scanner to match and no advisory to read. The flaw is that OpenSSL took the attacker's word for it. Every TLS handshake message carries a 4-byte header, three bytes of which declare how long the body will be. Older versions grew the receive buffer to that declared size the moment the header landed, before a single byte of the body showed up, and before the handshake's own checks ran. For an inbound ClientHello the ceiling is 131 KB. Then the worker thread blocks, waiting on a body that never comes. No authentication, no session, no key exchange. The memory does not come back On its own, that is a connection-exhaustion attack, and those are as old as Slowloris. What makes HollowByte stick is glibc. When the attacker drops the connection, OpenSSL frees the buffer, but glibc holds small and medium chunks for reuse rather than returning them to the kernel. The attack varies the claimed size on every connection, and in Okta's tests, that was enough to stop the allocator from reusing what it freed. The heap fragments, resident set size climbs, and it stays climbed long after the attacker has gone. In Okta's NGINX testing, a 1 GB server was OOM-killed with 547 MB of memory frozen in fragments. On a 16 GB server, HollowByte locked up 25% of system memory without ever crossing the connection ceiling, which is why the Red Team says "standard connection-limiting defenses won't stop it". Those figures are Okta's own, and it published no exploit code alongside them. The Hacker News found no public proof-of-concept repository on GitHub as of July 18. OpenSSL decided this wasn't a vulnerability The pull request from Matt Caswell, who wrote the patch, puts it plainly: the security team chose to "handle this as a 'bug or hardening' only fix". OpenSSL's own security policy defines four severity tiers, Critical down to Low, and "bug or hardening" is not among them. Even a Low issue earns a CVE, a changelog note, and an entry on the vulnerabilities page. HollowByte has none of the three. The Hacker News found no mention of the fix in the release notes or in all 23 entries of OpenSSL's 4.0.1 changelog. OpenSSL has not said why. Here is the case for them: 131 KB per connection is small, every TLS server allocates memory per connection, and a bounded allocation is not a vulnerability. Okta's answer is that the memory never comes back. The Hacker News has asked OpenSSL why HollowByte was triaged below Low, and whether the fix reached the extended-support 1.1.1 and 1.0.2 branches. It has also asked Okta whether the fragmentation survives allocators other than glibc. This story will be updated with any response. The project's line is finer than it looks. In January, OpenSSL assigned CVE-2025-66199, rated Low, to a TLS 1.3 certificate-compression bug in which a peer-supplied length grew a heap buffer before validation, worth around 22 MiB per connection. That one needed four things to line up: certificate compression compiled in, a compression algorithm available, the extension negotiated, and, on servers, client certificates requested. HollowByte needs none of them. The same June 9 release assigned CVE-2026-34183, rated Moderate, to unbounded memory growth in the QUIC PATH_CHALLENGE handler. Both are memory-exhaustion DoS. Both got numbers. The release also closed 18 CVEs, including a High-severity use-after-free in PKCS7_verify(), so anyone running one of those upstream builds has the fix without being told. Downstream is worse. Red Hat's documented default is to backport rather than move the version, so a patched package still reports the version it was built from. What normally resolves that is the advisory and the OVAL feed, both keyed to CVE names. There is no CVE here to key on. That leaves the package changelog or the maintainer: ask whether they rebased on the June 9 release or took the patch, which is pull request 30792 for master and 4.0, 30793 for 3.6, 3.5, and 3.4, and 30794 for 3.0. If you build OpenSSL yourself, upgrade to the listed release and restart whatever loaded the old one. The fix covers TLS only. Caswell wrote on the pull request that DTLS was left alone because doing it properly would have been far more invasive, and that the project decided not to bother with it for now. The Hacker News compared OpenSSL's source at the 3.6.2 and 3.6.3 tags and found the DTLS handshake file byte-identical across the fix. In 4.0.1, the newest release, that path still sizes its buffer from the length the peer declares. OpenSSL has not classified that path or committed to fixing it. The release notes, the changelog, and the vulnerabilities page say nothing about it. The pull request does. OpenSSL's triager calls it a deployment issue, not a protocol flaw Update (July 20, 2026): Alexandr Nedvedicky, the OpenSSL developer who triaged HollowByte, responded The Hacker News after publication. He separated HollowByte from the QUIC bug that did get a CVE this June. The QUIC flaw is a protocol problem, he said, because the code sets no limit on how many PATH_CHALLENGE frames it will accept. HollowByte, on his reading, comes down to a server left in a blocking mode with no limits set, closer to a deployment choice than a flaw in the protocol. He triaged the report on OpenBSD, which does not use glibc, and said he had "not considered any effects possibly coming from glibc." That behavior is the center of Okta's case. He was also unsure the shipped fix settles it. Caswell's patch grows the buffer conservatively but still uses realloc, and Nedvedicky said he was "not sure if it improves anything for glibc." Okta recommends upgrading regardless. On whether the fix reached the extended-support 1.1.1 and 1.0.2 branches, he declined to comment and pointed to OpenSSL's support portal. OpenSSL publishes its analysis Update (July 24, 2026): OpenSSL has set out its reasoning on the HollowByte report. It reproduced the behavior on glibc/Linux: resident memory does stay elevated after the attacking connections close, because the allocator holds freed memory for reuse. In OpenSSL's testing, that elevation reached a plateau set by peak concurrent handshakes and was then reused rather than climbing across repeated rounds, including under randomized message sizes and on both patched and unpatched builds. The project describes the residual cost as "a bounded, one-time increase set by peak concurrency, not an accumulating leak." Its reasoning for the classification is bounded against unbounded impact. The PATH_CHALLENGE issue grew without limit and no application setting could neutralize it, so only a library change could close it. HollowByte's allocation is capped per connection, and OpenSSL puts the outages in the slow-connection class that timeouts, connection caps and non-blocking I/O already address. On a normally-resourced host it saw worker exhaustion rather than out-of-memory; the OOM result in Okta's tests was on a memory-constrained box. It calls the classification a judgement and says it will revisit if new information changes the analysis. The fix was developed in public pull requests, and withholding a CVE was a deliberate classification. The project accepts that a fix developed in the open is not the same as one a defender can readily find, and says it has since added a CHANGES.md entry recording the change and the releases carrying it. Two open questions are answered. OpenSSL 1.1.1 and 1.0.2 are out of public support and maintained under extended-support contracts, whose customers receive the change through their supported releases. DTLS is confirmed unchanged, with the per-message maximum still bounding the allocation, and the project treats incremental handling there as unfinished rather than rejected. OpenSSL's nginx figures put worst-case peak resident memory per worker at roughly 102 MB before the change and 53 MB after, with every connection declaring a large message; under a realistic mix of sizes, roughly 70 MB down to 55 MB. Its guidance is to upgrade and, separately, to set handshake and idle timeouts, cap concurrent connections, rate-limit per source, and prefer non-blocking I/O.
thehackernews.comJul 17, 2026extracted
HollowByte DDoS flaw bloats OpenSSL server memory with 11-byte payload
A vulnerability dubbed HollowByte allows unauthenticated attackers to trigger a denial-of-service (DoS) condition on OpenSSL servers with a malicious payload of just 11 bytes. The OpenSSL team has silently fixed the vulnerability (no identifier assigned) and backported the patch to older releases. Because the OpenSSL software is the foundational backbone for secure internet communication, organizations should prioritize switching to a fixed version of the library. HollowByte details In an advisory earlier this week, Okta’s Red Team described how the HollowByte DoS vulnerability works and its impact in a real-world scenario. The researchers explain that in a TLS handshake, each message has a 4-byte header for declaring the size of the incoming message. However, vulnerable OpenSSL versions allocate the declared length before receiving the payload and checking its size. Every TLS handshake message begins with a 4-byte handshake header, where a three-byte length field discloses the size of the handshake data that should follow. Without validating the payload, the server trusts the packet's claims and allocates the indicated memory. "The worker thread then blocks, waiting indefinitely for data that will never arrive," Okta explains. An unauthenticated attacker can trigger HollowByte by opening a TLS connection and sending an 11-byte malicious input with a header declaring that a much larger message body will follow. The attacker repeats the same process across multiple connections, causing the server to allocate considerable amounts of memory via a relatively small volume of transmitted data. Okta researchers note that while OpenSSL frees the buffers when a connection drops, the GNU C Library (glibc) has a different way to handle memory and "does not immediately return small-to-medium allocations to the operating system; it keeps them for potential reuse." “By launching waves of connections with randomized claimed sizes, an attacker prevents the allocator from reusing those freed chunks,” Okta says. “The heap fragments heavily, causing the server’s Resident Set Size (RSS) to climb continuously. Even after the attacker disconnects, the server remains permanently bloated.” The only way to fully reclaim the space is by restarting the process. Impact and fixes The open-source OpenSSL library is embedded in popular software projects such as NGINX and Apache web servers, language runtimes (e.g., Node.js, Python, Ruby, PHP), and databases (MySQL, PostgreSQL). It comes pre-installed on most Linux distributions for TLS encryption and certificate handling. In Okta’s tests on NGINX showed that low-capacity environments can be easily depleted of memory using HollowByte, while higher-spec servers may lose up to 25% of their memory while the attack bandwidth remains below security alerting thresholds. Although DoS flaws are considered less severe than vulnerabilities that enable data theft or code execution, they can cause operational disruptions and reputational damage. The HollowByte DoS issue has been fixed in OpenSSL 4.0.1 and backported to versions 3.6.3, 3.5.7, 3.4.6, and 3.0.21, which now grow the buffer only when the data arrives, ignoring header claims. Despite being addressed as a "hardening fix" and not a security vulnerability, Okta recommends "upgrading your distribution's OpenSSL packages immediately." Overall prevention scores can hide what happens after initial access. Once attackers are using valid credentials, prevention drops sharply. The Blue Report 2026 measures defenses technique by technique across 338 million simulations run in customer production environments. Get the report
bleepingcomputer.comJul 17, 2026extracted
PHP利用者は見逃し厳禁 TLS通信でサービス停止を招くHigh脆弱性を修正
PHP�ɍ��댯�x�̐Ǝ㐫��������A�C���ł����J���ꂽ�B����TLS�ڑ����̃G���[�����ɂ���A����̊��ł�HTTPS�ʐM�̎��s�����������ɃT�[�r�X��~�ɔ��W���鋰�ꂪ����Ƃ����B ���̋L���͉������ł��B����o�^�i�����j����ƑS�Ă������������܂��B �@The PHP Group�́APHP�ɉe�����镡���̐Ǝ�i�������Ⴍ�j�����C�������B���ɁuCVE-2026-12184�v�́ATLS�ڑ����̃G���[�����̕s���ɂ��APHP-FPM����DoS�iDenial of Service�j�U���������N�������ꂪ���鍂�댯�x�̐Ǝ㐫���B �@�����āA�Í������C�u�����uOpenSSL�v�g���ɑ��݂��郁�����j���̖��uCVE-2026-14355�v���C�����Ă���A�Ώۃ��[�U�[�ɏC���łւ̍X�V���Ăъ|���Ă���B �@CVE-2026-12184�́AGitHub Security Advisory�uGHSA-mhmq-mmqj-2v39�v�Ō��\���ꂽ�Ǝ㐫���B�e������̂�PHP 8.3.32�����A8.4.21�����A8.5.6�����ŁA�C���ł͂��ꂼ��8.3.32�A8.4.21�A8.5.6�ƂȂ�B���ʐƎ㐫�]���V�X�e���iCVSS�jv4.0�̃X�R�A��8.2�ŁA�[���x�́uHigh�v�ƕ]������Ă���B�@�����⊮�S���ւ̉e���͊m�F����Ă��Ȃ�����A�p���ւ̉e���͍����B �@�����́ATLS�ڑ����̃G���[�����ɂ���BTLS�Í����̏������Ɏ��s����Ɠ����X�g���[���͔j������邪�A���̌�̏����ŏ�Ԋm�F���K�Ɏ��s����Ȃ����߁A�s���ȃ������A�N�Z�X���������鋰�ꂪ����B �@���̖��́A�ؖ����̗L���������ڑ���̏ؖ������؎��s�Ȃǂɂ����TLS�ڑ����m���ł��Ȃ������Ƃ��ɔ�������\��������B�U���҂�����ȓ��͂𑗂荞�ރ^�C�v�̐Ǝ㐫�ł͂Ȃ��ATLS�ڑ����s���̏����s���������ƂȂ�_���������B �@���ɉe�����傫���̂�PHP-FPM�����B��Q�����������FPM�v���Z�X�S�̂���~���A�z���̃��[�J�[�v���Z�X�������ɗ��p�ł��Ȃ��Ȃ�B���̂��߁A�O��HTTPS�T�[�r�X�ƘA�g����PHP�A�v���P�[�V�����ł́ATLS�ڑ����s���_�@�Ƃ��ăT�[�r�X�Ɏx�Ⴊ�����鋰�ꂪ����B�����_�ʼn����͌��\����Ă��炸�A�C���łւ̍X�V���B��̑�ƂȂ�B �@�����Ɍ��J���ꂽCVE-2026-14355�́AOpenSSL�g����openssl_encrypt����AES-WRAP-PAD�A���S���Y���𗘗p�����ꍇ�ɔ�������Ǝ㐫���B�e������̂�PHP 8.2.32�����A8.3.32�����A8.4.23�����A8.5.8�����ŁA�C���ł�8.2.32�A8.3.32�A8.4.23�A8.5.8�Ƃ��Č��J���ꂽ�BCVSS v3.1�̃X�R�A��4.8�ŁA�[���x�́uMedium�v�ƕ]������Ă���B �@�����́A�Í�����̃f�[�^�T�C�Y�𐳂������ς��炸�Ƀ������̈���m�ۂ��Ă������Ƃɂ���B���̌��ʁAOpenSSL���m�ۍςݗ̈���ăf�[�^���������݁A�������j������������B��Q�͂��̌�̃������Ǘ������Ō��o����A�A�v���P�[�V������~�ɂȂ���\��������B �@AES-WRAP-PAD��Web�A�v���P�[�V�����ōL�����p�����A���S���Y���ł͂Ȃ����߁A�e��������͌���I�Ƃ݂���B����A�Y������������̗p���Ă���ꍇ�́A�A�v���P�[�V������~��DoS�ɂȂ��鋰�ꂪ���邽�ߒ��ӂ��K�v���B �@PHP�J�����͗��Ǝ㐫�̏C���ł����J���Ă���B���ɊO��HTTPS�ʐM������PHP-FPM���ł́ACVE-2026-12184�̉e�����傫�����Ƃ���D��I�ȍX�V�����߂���BCVE-2026-14355�ɂ��Ă��A�Y����������𗘗p���Ă�����ł́A�����ďC���łւ̃A�b�v�f�[�g��i�߂����B Copyright © ITmedia, Inc. All Rights Reserved.
atmarkit.itmedia.co.jpJul 8, 2026extracted
OpenSSLに高危険度の脆弱性 発見にはClaudeが関与
OpenSSL�v���W�F�N�g�́APKCS#7�������؋@�\�ɍ��댯�x�̉����g�p���ׂ�����ƌ��\�����B�H�ς݃��b�Z�[�W�ňُ퓮�삪�����A�N���b�V��������j��A���u�R�[�h���s�̋��ꂪ����A�C���Ō��J�ōX�V���Ăт������B ���̋L���͉������ł��B����o�^�i�����j����ƑS�Ă������������܂��B �@OpenSSL�v���W�F�N�g��2026�N6��9���i���n���ԁj�A�Í������C�u�����uOpenSSL�v�ɍ��댯�x�̐Ǝ�i�������Ⴍ�j���uCVE-2026-45447�v�����݂���ƌ��\���A�C���ł����J�����B�Ώۊ��ł̓N���b�V��������j�������鋰�ꂪ����A��������ł͉��u����C�ӃR�[�h�����s�����\��������B �@����PKCS#7�������؏����Ŕ�������q�[�v�̈�̉����g�p�iUAF�j�ɕ��ނ���錇�ׂŁA�H�ς݂�PKCS#7�܂���S/MIME�����t�����b�Z�[�W�����������ۂɗU�������BSignedData����digestAlgorithms�t�B�[���h�����ASN.1 SET�Ƃ��Ĕz�u���ꂽ�ꍇ�APKCS7_verify���Ăяo�����Ǘ���BIO������ĉ�����A���̌�ɃA�v���P�[�V������������BIO�ɃA�N�Z�X����ƕs���ȃ������Q�ƂɎ���B �@�T�^��ł̓A�v���P�[�V�������Y��BIO��BIO_free�����{�����i�K�ňُ킪��������B�e���̓��e�̓��������蓖�ĕ���������ɂ���ĈقȂ���̂́A�v���Z�X��~��q�[�v�j���ɂȂ���\��������B���p���ɂ���Ă͍U���҂ɂ��R�[�h���s�ɔ��W����]�n������B �@�e������̂�OpenSSL��PKCS#7 API���g����PKCS#7�܂���S/MIME�������b�Z�[�W����������A�v���P�[�V�����BCMS API�𗘗p��������͑ΏۊO�Ƃ��ꂽ�B �@OpenSSL�ɂ��ƁA4.0�n�A3.6�n�A3.5�n�A3.4�n�A3.0�n�A1.1.1�n�A1.0.2�n���e������B���p�҂ɂ�4.0.1�A3.6.3�A3.5.7�A3.4.6�A3.0.21�ւ̍X�V�����߂Ă���B1.1.1�n��1.0.2�n�̓v���~�A���T�|�[�g�_��җp�̏C���ł������BFIPS���W���[���͉e���͈͊O�ŁA�����ƂȂ����R�[�h��FIPS���W���[�����E�̊O���ɑ��݂��邽�߂Ɛ������Ă���B �@����̌��ׂ̔����ɂ̓Z�L�����e�B�����҂����łȂ��AAnthropic Research����сuClaude�v���֗^�����Ƃ����B�܂��������\���ꂽ18���̐Ǝ㐫�̂���7���ɂ����āAAnthropic�̃Z�L�����e�B�����҂��҂܂��͋����҂Ƃ��ăN���W�b�g����Ă���B �@�ߔN��OpenSSL�ł͍��댯�x�]���̐Ǝ㐫���\�����͑����Ȃ��A����̎��Ă�2026�N�Ɋm�F���ꂽ���댯�x�Č��̈�Ƃ��Ē��ڂ��W�߂Ă���BAI�Z�p���Ǝ㐫�����v���Z�X�Ɋ��p���ꂽ����Ƃ��Ă��S���W�߂������B Copyright © ITmedia, Inc. All Rights Reserved.
atmarkit.itmedia.co.jpJun 12, 2026extracted
世界中のWebサーバが影響 Apacheが危険な脆弱性を一斉修正
Apache HTTP Server�ɑ�K�͂ȏC�����������B�ŐV�łł�HTTP/2�������͂��߁A�v���L�V��SSL�A�F�؋@�\�ȂǍL�͈͂ɋy�ԐƎ㐫�ɑΏ����Ă���B�T�[�r�X��~������j��ɂȂ��鋰�ꂪ��������܂܂�Ă������ߋ}���C�����Ăق����B ���̋L���͉������ł��B����o�^�i�����j����ƑS�Ă������������܂��B �@Apache Software Foundation��2026�N6��8���i�č����ԁj�A�uApache HTTP Server 2.4.68�v�����J�����B2.4�n�̍ŐV�łɈʒu�t�������ʒłŁA�Z�L�����e�B�C����s��C���A�@�\�lj����܂ލX�V�ƂȂ�B�J�����͏]���ŗ��p�҂ɑ��A2.4.68�ւ̍X�V�𐄏����Ă���B �@Apache HTTP Server 2.4.68�ł͑����̐Ǝ�i�������Ⴍ�j�����C�����ꂽ�B����HTTP/2�����ɂ����錇�ׂł���uCVE-2026-49975�v�����ڂ����B���Ǝ㐫�͍H���ꂽHTTP���N�G�X�g�ɂ���ĉߏ�ȃ������m�ۂ��������A�T�[�r�X��~�Ɏ��鋰�ꂪ�������B���̑��ɂ͂ǂ̂悤�ȐƎ㐫���������̂��B �@�������umod_http2�v�ɂ����āuCVE-2026-48913�v���C�����ꂽ�B�t�@�C���f�B�X�N���v�^�͊����ɉ���ς݃������ɃA�N�Z�X����uUse-After-Free�i�����g�p�j�v�̖��ŁA�������j����ُ�I���������N�����댯���������B �@�ݒ�t�@�C�����̐��K�\�������ɋN������uCVE-2026-44631�v���[���Ȗ��̈�������B�����t�������̃I�[�o�[�t���[�ɂ���ăq�[�v�A���_�[�t���[���������A�H���ꂽ���K�\�����烁�����j��ɂȂ���\�����������B �@�v���L�V�֘A���W���[���ł������̌��ׂ��������ꂽ�B�uCVE-2026-34355�v�́umod_proxy_html�v�ɑ��݂����o�b�t�@�[�I�[�o�[�t���[�Ƃ���A�s���ȃo�b�N�G���h���瑗�M���ꂽ�f�[�^�ɂ���ăv���Z�X�ُ�I�����������鋰�ꂪ�������B�uCVE-2026-34356�v�ɂ����āA�uProxyPassReverseCookieMap�v�����Ƀq�[�v�x�[�X�̃o�b�t�@�[�I�[�o�[�t���[�����݂��A���ӂ���o�b�N�G���h�T�[�o�o�R�ň��p�����댯���w�E����Ă����B �@�����Ǘ��Ɋւ�����Ƃ��ẮuCVE-2026-44119�v���C���ΏۂƂȂ����B�u.htaccess�v���̎��]���@�\�����p���邱�ƂŁA���[�J�����p�҂�httpd���s�������Ńt�@�C�����Q�Ƃł���\�����������B �@SSL�@�\�ł́uCVE-2026-44185�v�ɑΏ������B���Ǝ㐫�ɂ����ẮA�U���ҊǗ�����OCSP�iOnline Certificate Status Protocol�j�T�[�o�Ƃ̒ʐM���Ƀo�b�t�@�[�̉ߓǂݍ��݂��������鋰�ꂪ����Amod_ssl���p���ɉe������BFTP�v���L�V�@�\�ł��A�uCVE-2026-44186�v�̖������[�v����A�uCVE-2026-29170�v�̃N���X�T�C�g�X�N���v�e�B���O�iXSS�j�̐Ǝ㐫���C�����ꂽ�B �@���̑��A�uCVE-2026-42536�v�imod_xml2enc�̃q�[�v�I�[�o�[�t���[�j��A�uCVE-2026-42535�v�imod_dav_fs�̕ی�̈摀����j�A�uCVE-2026-29167�v�imod_ldap�̉����g�p�j�A�uCVE-2026-43951�v�imod_headers�����mod_mime���p���͈̔͊O�ǂݍ��݁j�ȂǑ���ɂ킽��Ǝ㐫�ɑΉ����Ă���B �@�@�\�ʂɂ����ẮAmod_ssl�����ab��OpenSSL 4.0���T�|�[�g�������ASSL�ؖ��������̊g�[��N���C�A���g�ؖ����F�؎��̎��ʉ��P�����������B���O�@�\�ł�ErrorLogFormat�Ƀ~���b�P�ʂ̎����o�͂�lj����Ă���B �@HTTP/2�������X�V����Amod_http2�̓o�[�W����2.0.42�ɍ��V���ꂽ�B�t�@�C�����M���̃t�@�C���f�B�X�N���v�^���p�������P��ACookie�w�b�_�����A�s�K�ȃG���[�����ȂǕ����̖�肪�C������Ă���B �@Apache HTTP Server�͐��E����Web�T�[�o��ՂōL�����p����Ă���B����̍X�V�ł�2.4.0�`2.4.67�̍L�͈͂ɉe������Ǝ㐫��������������Ă���A�^�p���̊Ǘ��҂ɂ͑��₩�ȍX�V�K�p�����߂���B Copyright © ITmedia, Inc. All Rights Reserved.
atmarkit.itmedia.co.jpJun 10, 2026extracted
AISLE Snapshot keeps source code under enterprise control during vulnerability scanning
AISLE Snapshot keeps source code under enterprise control during vulnerability scanning AISLE has introduced AISLE Snapshot, a new offering that gives regulated and security-sensitive enterprises access to frontier-class vulnerability detection inside their own environments, at a fraction of the cost, with source code and security data that never leave their control. Organizations are under increasing pressure to secure growing codebases against a rapidly expanding vulnerability landscape. Reported CVEs are up 42.5% year-over-year through mid-2026, and attackers are leveraging AI to accelerate discovery and exploitation at the same pace. Yet many organizations remain locked out of the best tools by data sovereignty, compliance, and operational constraints. AISLE Snapshot deploys AISLE’s frontier-class vulnerability discovery technology directly inside the customer’s private cloud, on-premises, or fully air-gapped environment, eliminating the data sovereignty and compliance barriers that have kept the best tools out of reach. Organizations receive verified findings prioritized by business impact, with the full context needed to move from discovery to remediation without delay. “The organizations with the greatest pressure to secure software often face the strictest requirements around privacy, sovereignty, and operational control,” said Ondrej Vlcek, CEO of AISLE. “They can’t send their code to external services, but they also can’t afford to wait or to throw more people at the problem. “AISLE Snapshot is designed to be up and running quickly, with no added strain on security teams. And because we’re smart about model selection, matching the right model to the right task rather than defaulting to frontier, organizations get faster performance at a fraction of the cost. The result isn’t a raw dump of findings. It’s verified, prioritized intelligence that security teams can act on immediately.” Frontier-class detection without frontier-class costs AISLE Snapshot delivers vulnerability discovery at approximately 10 times greater cost efficiency than frontier models such as Anthropic’s Mythos. Snapshot also extends that efficiency through triage, prioritizing findings across large codebases and broad software portfolios without prohibitive infrastructure costs. Organizations using AISLE Snapshot can: Achieve detection — powered by a combination of AI-based code analysis and AI-guided fuzzing Act on findings, not noise — receive verified, business impact-prioritized results with a false positive rate under 5% Deploy anywhere — public cloud, private cloud, on-premises, or fully air-gapped, with no compromise on capability Leverage the right model for the job — use AISLE-optimized cybersecurity LLMs or existing models to maximize performance and cost efficiency See their full exposure in days — with no added strain on security teams Budget with confidence — flat, predictable pricing independent of token usage To date, AISLE has discovered and responsibly disclosed more than 225 CVEs across widely used software projects, including OpenSSL, Linux, cURL, Apache, Mozilla, Redis, OpenEMR, and Elastic. While Snapshot is focused on vulnerability discovery and prioritization, it is built on the same platform that enables AISLE’s closed-loop approach to vulnerability management, spanning discovery, prioritization, remediation, verification, and self-improvement.
helpnetsecurity.comJun 10, 2026extracted
USN-8414-2: OpenSSL vulnerabilities
Packages openssl - Secure Socket Layer (SSL) cryptographic library and tools openssl1.0 - Secure Socket Layer (SSL) cryptographic library and tools Details USN-8414-1 fixed several vulnerabilities in OpenSSL. This update provides the corresponding update for Ubuntu 14.04 LTS, Ubuntu 16.04 LTS, Ubuntu 18.04 LTS, and Ubuntu 20.04 LTS. Original advisory details: Frank Buss discovered that OpenSSL had a heap buffer over-read in ASN.1 content parsing. An attacker could possibly use this issue to cause OpenSSL to crash, resulting in a denial of service, or obtain sensitive information. (CVE-2026-34180) Asim Viladi Oglu Manizada and Alex Gaynor discovered that OpenSSL could accept forged CMS AuthEnvelopedData messages. An attacker could possibly use this issue to bypass message authentication checks. (CVE-2026-34182) Mayank Jangid, Kushal Khemka, Hari Priandana, Bhabani Sankar Das, and Qifan Zhang discovered that OpenSSL had a possible NULL dereference in password- based CMS decryption. An attacker... USN-8414-1 fixed several vulnerabilities in OpenSSL. This update provides the corresponding update for Ubuntu 14.04 LTS, Ubuntu 16.04 LTS, Ubuntu 18.04 LTS, and Ubuntu 20.04 LTS. Original advisory details: Frank Buss discovered that OpenSSL had a heap buffer over-read in ASN.1 content parsing. An attacker could possibly use this issue to cause OpenSSL to crash, resulting in a denial of service, or obtain sensitive information. (CVE-2026-34180) Asim Viladi Oglu Manizada and Alex Gaynor discovered that OpenSSL could accept forged CMS AuthEnvelopedData messages. An attacker could possibly use this issue to bypass message authentication checks. (CVE-2026-34182) Mayank Jangid, Kushal Khemka, Hari Priandana, Bhabani Sankar Das, and Qifan Zhang discovered that OpenSSL had a possible NULL dereference in password- based CMS decryption. An attacker could possibly use this issue to cause OpenSSL to crash, resulting in a denial of service. (CVE-2026-42766) Zhanpeng Liu, Guannan Wang, and Guancheng Li discovered that OpenSSL had a NULL pointer dereference in CRMF EncryptedValue decryption. An attacker could possibly use this issue to cause OpenSSL to crash, resulting in a denial of service. (CVE-2026-42767) Thai Duong discovered that OpenSSL had a heap use-after-free in PKCS7_verify(). An attacker could possibly use this issue to cause OpenSSL to crash, resulting in a denial of service, or execute arbitrary code. (CVE-2026-45447) Zehua Qiao and Jinwen He discovered that OpenSSL had a possible heap buffer overflow in ASN.1 multibyte string conversion. An attacker could possibly use this issue to cause OpenSSL to crash, resulting in a denial of service, or execute arbitrary code. (CVE-2026-7383) Bhabani Sankar Das discovered that OpenSSL had an out-of-bounds read in CMS password-based decryption. An attacker could possibly use this issue to cause OpenSSL to crash, resulting in a denial of service. (CVE-2026-9076) The problem can be corrected by updating your system to the following package versions: Reduce your security exposure Ubuntu Pro provides ten-year security coverage to 25,000+ packages in Main and Universe repositories, and it is free for up to five machines.
ubuntu.comJun 9, 2026extracted
USN-8414-1: OpenSSL vulnerabilities
Details Frank Buss discovered that OpenSSL had a heap buffer over-read in ASN.1 content parsing. An attacker could possibly use this issue to cause OpenSSL to crash, resulting in a denial of service, or obtain sensitive information. (CVE-2026-34180) Pavol Zacik and Alex Gaynor discovered that OpenSSL incorrectly accepted PKCS#12 files with short HMAC keys when using PBMAC1. An attacker could possibly use this issue to bypass integrity checks. This issue only affected Ubuntu 25.10 and Ubuntu 26.04 LTS. (CVE-2026-34181) Asim Viladi Oglu Manizada and Alex Gaynor discovered that OpenSSL could accept forged CMS AuthEnvelopedData messages. An attacker could possibly use this issue to bypass message authentication checks. (CVE-2026-34182) Abhinav Agarwal discovered that OpenSSL had unbounded memory growth in the QUIC... Frank Buss discovered that OpenSSL had a heap buffer over-read in ASN.1 content parsing. An attacker could possibly use this issue to cause OpenSSL to crash, resulting in a denial of service, or obtain sensitive information. (CVE-2026-34180) Pavol Zacik and Alex Gaynor discovered that OpenSSL incorrectly accepted PKCS#12 files with short HMAC keys when using PBMAC1. An attacker could possibly use this issue to bypass integrity checks. This issue only affected Ubuntu 25.10 and Ubuntu 26.04 LTS. (CVE-2026-34181) Asim Viladi Oglu Manizada and Alex Gaynor discovered that OpenSSL could accept forged CMS AuthEnvelopedData messages. An attacker could possibly use this issue to bypass message authentication checks. (CVE-2026-34182) Abhinav Agarwal discovered that OpenSSL had unbounded memory growth in the QUIC PATH_CHALLENGE handler. A remote attacker could possibly use this issue to cause OpenSSL to use excessive resources, leading to a denial of service. This issue only affected Ubuntu 25.10 and Ubuntu 26.04 LTS. (CVE-2026-34183) Sunwoo Lee, Hyuk Lim, and Seunghyun Yoon discovered that OpenSSL had a NULL pointer dereference in QUIC server initial packet handling. A remote attacker could possibly use this issue to cause OpenSSL to crash, resulting in a denial of service. This issue only affected Ubuntu 25.10 and Ubuntu 26.04 LTS. (CVE-2026-42764) Mayank Jangid, Kushal Khemka, Hari Priandana, Bhabani Sankar Das, and Qifan Zhang discovered that OpenSSL had a possible NULL dereference in password- based CMS decryption. An attacker could possibly use this issue to cause OpenSSL to crash, resulting in a denial of service. (CVE-2026-42766) Zhanpeng Liu, Guannan Wang, and Guancheng Li discovered that OpenSSL had a NULL pointer dereference in CRMF EncryptedValue decryption. An attacker could possibly use this issue to cause OpenSSL to crash, resulting in a denial of service. (CVE-2026-42767) Alex Gaynor discovered that OpenSSL had a Bleichenbacher oracle in CMS_decrypt() and PKCS7_decrypt() with multiple RecipientInfo values. An attacker could possibly use this issue to obtain sensitive information. This issue only affected Ubuntu 25.10 and Ubuntu 26.04 LTS. (CVE-2026-42768) Alex Gaynor discovered that OpenSSL had a trust-anchor substitution issue in CMP rootCaKeyUpdate processing. An attacker could possibly use this issue to bypass certificate trust validation. This issue only affected Ubuntu 25.10 and Ubuntu 26.04 LTS. (CVE-2026-42769) Alex Gaynor discovered that OpenSSL used attacker-supplied parameters when validating FFC-DH peers. An attacker could possibly use this issue to weaken key validation and compromise security guarantees. (CVE-2026-42770) Alex Gaynor discovered that OpenSSL could ignore the IV in AES-OCB mode on the EVP_Cipher() path. An attacker could possibly use this issue to bypass cryptographic protections and obtain sensitive information. (CVE-2026-45445) Alex Gaynor discovered that OpenSSL had incorrect tag processing for empty messages in AES-GCM-SIV and AES-SIV modes. An attacker could possibly use this issue to bypass cryptographic integrity checks. (CVE-2026-45446) Thai Duong discovered that OpenSSL had a heap use-after-free in PKCS7_verify(). An attacker could possibly use this issue to cause OpenSSL to crash, resulting in a denial of service, or execute arbitrary code. (CVE-2026-45447) Zehua Qiao and Jinwen He discovered that OpenSSL had a possible heap buffer overflow in ASN.1 multibyte string conversion. An attacker could possibly use this issue to cause OpenSSL to crash, resulting in a denial of service, or execute arbitrary code. (CVE-2026-7383) Bhabani Sankar Das discovered that OpenSSL had an out-of-bounds read in CMS password-based decryption. An attacker could possibly use this issue to cause OpenSSL to crash, resulting in a denial of service. (CVE-2026-9076) The problem can be corrected by updating your system to the following package versions: Reduce your security exposure Ubuntu Pro provides ten-year security coverage to 25,000+ packages in Main and Universe repositories, and it is free for up to five machines.
ubuntu.comJun 9, 2026extracted
OpenSSL Patches High-Severity Vulnerability Found With AI
The latest OpenSSL releases patch 18 vulnerabilities, including a high-severity issue that could allow remote code execution. The high-severity vulnerability, tracked as CVE-2026-45447, is a heap user-after-free bug in a function used for PKCS#7 (Public-Key Cryptography Standard #7) verification. Discovered by a Calif researcher in collaboration with Claude AI and Anthropic Research, the bug can be triggered using a specially crafted PKCS#7 or S/MIME signed message during PKCS#7 signature verification. “When processing a PKCS#7 or S/MIME signed message, if the SignedData digestAlgorithms field is present as an empty ASN.1 SET, OpenSSL may incorrectly free a caller-owned BIO during PKCS7_verify(). A subsequent use of the BIO by the calling application results in a use-after-free condition,” OpenSSL developers explained. Exploitation of the vulnerability can result in heap corruption, process crashes, and possibly in remote code execution. The moderate-severity flaws patched in OpenSSL can be exploited to decrypt encrypted communications, forge arbitrary ciphertexts, launch DoS attacks, bypass integrity validation, and execute arbitrary code. One of the medium-severity weaknesses can be exploited to trick a system into accepting a fake, attacker-controlled certificate and private key, allowing the attacker to bypass authentication mechanisms with a 1-in-256 success rate. The low-severity vulnerabilities can lead to crashes (DoS), message forgery, recovery of private keys, replacement of root CA certificates, and possibly arbitrary code execution. Alex Gaynor of Anthropic has been credited with reporting half a dozen of the newly patched vulnerabilities, suggesting that the AI giant’s Mythos model may have helped identify the flaws. High-severity vulnerabilities in OpenSSL are rare these days. Only one high-severity issue was patched last year, and CVE-2026-45447 is the second high-severity flaw of 2026. In April, OpenSSL developers patched a flaw that can allow an attacker to obtain sensitive data. Related: Drupal Patches Highly Critical Vulnerability Exposing Websites to Hacking Related: Google Patches 5th Chrome Zero-Day Exploited in 2026 Related: Android Update Patches Exploited Zero-Day, 123 Other Vulnerabilities Related: Oracle’s First Monthly Patches Resolve 77 Vulnerabilities
securityweek.comJun 9, 2026extracted
Debian 13.5 point release lands with security fixes, bug patches
Debian 13.5 point release lands with security fixes, bug patches Debian 13.5 is the fifth point release for the stable distribution “trixie.” The update folds in roughly 100 Debian Security Advisories and corrections for more than 130 source packages, covering everything from the Linux kernel and Apache HTTP Server to OpenSSH, sudo, systemd, OpenSSL, glibc, and FreeRDP. Fresh installer images carrying the same fixes will follow at the regular download locations. Sysadmins running trixie do not need to reinstall. Existing media remain valid, and machines already pulling from security.debian.org will find that most of the patches in 13.5 are already on disk. The headline items include a new Apache upstream release that closes an authentication bypass and a use-after-free flaw, a privilege escalation fix in sudo, an nspawn container escape patch in systemd, multiple OpenSSH corrections affecting scp and key handling, and a sweeping FreeRDP3 update that resolves dozens of CVEs. One package, dav4tbsync, was withdrawn because Thunderbird 140 now covers its functionality. Wide range of package corrections The miscellaneous bugfix section covers more than a hundred source packages. Apache HTTP Server moves to a new upstream stable release that addresses a use-after-free flaw (CVE-2026-23918), a privilege escalation issue (CVE-2026-24072), an authentication bypass (CVE-2026-33006), HTTP response splitting (CVE-2026-33523), and several out-of-bounds read and NULL pointer dereference conditions. OpenSSH receives corrections covering scp behavior around setuid and setgid bits (CVE-2026-35385), a command execution flaw (CVE-2026-35386), incomplete enforcement of PubkeyAcceptedAlgorithms and HostbasedAcceptedAlgorithms for ECDSA keys (CVE-2026-35387), connection multiplexing handling in proxy mode (CVE-2026-35388), and the authorized_keys “principals” option (CVE-2026-35414). Sudo gains a fix for a privilege escalation flaw (CVE-2026-35535). Systemd moves to a new upstream stable release and addresses an nspawn container escape (CVE-2026-40226), code execution issues (CVE-2026-40225 and CVE-2026-4105), and a freeze condition (CVE-2026-29111). The glibc package corrects DNS response handling errors tracked as CVE-2026-4437 and CVE-2026-4438, along with an assertion failure (CVE-2026-4046). FreeRDP3 sees one of the largest single-package updates, with corrections for dozens of CVEs spanning use-after-free conditions, buffer overflows, out-of-bounds reads, and denial of service flaws. The OpenSSL package also moves to a new upstream stable release. Other notable packages receiving security or stability fixes include curl, nginx, rsync, jq, jpeg-xl, libarchive, libcap2, sed, nano, exim4, dovecot, and python3.13. Security advisories rolled in The release incorporates roughly one hundred Debian Security Advisories. Among the packages covered are the Linux kernel, Chromium, Firefox ESR, Thunderbird, OpenSSL, OpenSSH, BIND 9, MediaWiki, GIMP, MuPDF, Pillow, Roundcube, Dovecot, Tor, OpenJDK 21, OpenJDK 25, Apache HTTP Server, Wireshark, LibreOffice, Prosody, strongSwan, and several PowerDNS components. Three separate kernel advisories appear in the list, reflecting ongoing Linux maintenance across the trixie cycle. Installer and infrastructure The Debian Installer was rebuilt to include the fixes pulled into stable through this point release, including a bump of the Linux ABI to 6.12.86+deb13. Supporting data packages received routine refreshes. The tzdata package picks up an updated time zone database with corrections for British Columbia, and distro-info-data adds an entry for Ubuntu 26.10 “Stonking Stingray.” The libdatetime-timezone-perl package was updated to match the new tzdata. Administrators can apply the changes by running their normal package management update against any Debian mirror.
helpnetsecurity.comMay 17, 2026extracted
OpenSSL 4.0.0 release cuts deprecated protocols and gains post-quantum support
OpenSSL 4.0.0 release cuts deprecated protocols and gains post-quantum support OpenSSL 4.0.0 removes several long-deprecated features, adds support for Encrypted Client Hello, and introduces API-level changes that will require code updates for applications built against older versions. SSLv3, SSLv2 client hello, and engines are gone SSLv3 support has been removed. The protocol was deprecated in 2015, and OpenSSL had it disabled by default since version 1.1.0 in 2016. Support for the SSLv2 Client Hello has also been removed. The engine API, which provided a mechanism for integrating external cryptographic hardware and software implementations, has been removed entirely. The no-engine build option and the OPENSSL_NO_ENGINE macro are now always present. Deprecated custom EVP_CIPHER, EVP_MD, EVP_PKEY, and EVP_PKEY_ASN1 methods have also been cut, along with deprecated fixed SSL/TLS version method functions and the error-state functions ERR_get_state(), ERR_remove_state(), and ERR_remove_thread_state(). Encrypted Client Hello and post-quantum additions The release adds support for Encrypted Client Hello (ECH) per RFC 9849, which allows the client hello message to be encrypted so passive observers cannot read the server name a client is connecting to. On the post-quantum side, the release adds the hybrid key exchange group curveSM2MLKEM768, the ML-DSA-MU digest algorithm, the cSHAKE function per NIST SP 800-185, and support for negotiated FFDHE key exchange in TLS 1.2 per RFC 7919. API and behavior changes that affect integrators ASN1_STRING has been made opaque. Signatures across a range of API functions, including those used in X.509 processing, now include const qualifiers where applicable. The functions X509_cmp_time(), X509_cmp_current_time(), and X509_cmp_timeframe() have been deprecated in favor of X509_check_certificate_times(). libcrypto no longer cleans up globally allocated data via atexit(). OPENSSL_cleanup() now runs in a global destructor, or not at all by default. BIO_f_reliable() has been removed with no replacement, having been broken since the 3.0 release. When X509_V_FLAG_X509_STRICT is set, AKID verification checks are now enforced, and the CRL verification process has received additional checks. Lower bounds checks are now enforced when using PKCS5_PBKDF2_HMAC with the FIPS provider. Build and tooling changes Support for deprecated elliptic curves in TLS per RFC 8422 and support for explicit EC curves are both disabled at compile time by default, with configuration options available to re-enable each. Build targets for darwin-i386 and darwin-ppc variants have been dropped. The c_rehash script has been removed in favor of openssl rehash. FIPS self-tests can now be deferred using the -defer_tests option of openssl fipsinstall. On Windows, the release adds support for choosing between static and dynamic Visual C++ runtime linkage. OpenSSL 4.0.0 is available on GitHub. Must read: 40 open-source tools redefining how security teams secure the stack Firmware scanning time, cost, and where teams run EMBA Subscribe to the Help Net Security ad-free monthly newsletter to stay informed on the essential open-source cybersecurity tools. Subscribe here!
helpnetsecurity.comApr 14, 2026extracted
RSA暗号の“失敗”を成功と誤認 OpenSSLで未初期化メモリが漏えいする恐れ
OpenSSL�ɕ����̐Ǝ㐫�����������B����̏������ŕs�K�ȏ����ɂ����R�����ɂȂ�����̂�����Ƃ����B�e���͈͕͂����o�[�W�����ɋy�сA�v���W�F�N�g�͏C���ς݃o�[�W�����ւ̍X�V���Ăъ|���Ă���B���̔w�i�ɂ͉�������̂��B ���̋L���͉������ł��B����o�^�i�����j����ƑS�Ă������������܂��B �@OpenSSL�v���W�F�N�g��2026�N4��7���i���n���ԁj�A�����C�u�����Ɋւ��镡���̐Ǝ�i�������Ⴍ�j�����C�������Ɣ��\�����B�����̒��ł��uCVE-2026-31790�v�͒����x�̐[���x�Ƃ���A����������Ŗ��������������̓��e���O���ɑ��M�����\��������Ƃ��Ē��ӂ��Ăъ|���Ă���B �@CVE-2026-31790�́ARSA�x�[�X�̌��J�v�Z�����iRSASVE�j�𗘗p����A�v���P�[�V�����ɉe������BRSA�Í��������̃G���[���ɕs�K�Ȗ߂�l�`�F�b�N�����s����邱�ƂŁA���������s���Ă��Ă������ƌ�F����A���������̃o�b�t�@�[���e���Í����Ƃ��Ĉ����鋰�ꂪ����B���ʂƂ��āA�A�v���P�[�V�����̉ߋ��̎��s���e�ȂNj@����U���҂ɘR��������\��������B �@���ɍU���҂��H����RSA���J�����������ɗ��p����P�[�X�Ń��X�N�����܂�B�����Ƃ��ẮA���̎��O���iEVP_PKEY_public_check�Ȃǁj�����{���邱�Ƃ��L���Ƃ����B �@�e������̂�OpenSSL 3.0�n�ȍ~�̕����o�[�W��������ёΉ�����FIPS���W���[���ŁAOpenSSL 1.1.1�����1.0.2�͂��̖��̉e�����Ȃ��B�e�o�[�W�����̗��p�҂ɂ́A3.0.20�A3.3.7�A3.4.5�A3.5.6�A3.6.2�ȂǏC���ς݃o�[�W�����ւ̃A�b�v�f�[�g����������Ă���B �@���̑��ɂ��A�����̒�X�N�̐Ǝ㐫������Ă���B�Ⴆ�uCVE-2026-28386�v�́A�����x86-64���iAVX-512�^VAES�Ή��j�ɂ����āAAES-CFB128�������ɍő�15�o�C�g�̋��E�O�ǂݎ�肪��������\��������Ƃ������̂��B��ɃN���b�V���ɂ��T�[�r�X���ہiDoS�j�U���ɂȂ��邪�A���R�����̃��X�N�͂Ȃ��Ƃ����B �@�܂��ADANE�֘A�̃N���C�A���g�����ɂ���������g�p�iuse-after-free�j�̉\���iCVE-2026-28387�j��ACMS���b�Z�[�W��������NULL�|�C���^�Q�ƁiCVE-2026-28389�ACVE-2026-28390�j�Ȃǂ����ꂽ�B�����͂����������������ŃA�v���P�[�V�����̃N���b�V���������N�������ꂪ����B �@����ɁAX.509�ؖ��������Ɋ֘A������Ƃ��āA�f���^CRL�iCertificate Revocation List�j��������NULL�|�C���^�Q�ƁiCVE-2026-28388�j��A32bit���ɂ�����q�[�v�o�b�t�@�[�I�[�o�[�t���[�iCVE-2026-31789�j���m�F����Ă���B �@����̈�A�̐Ǝ㐫�́A�������������������I�ȗ��p�V�i���I�Ŕ�������P�[�X���������̂́AOpenSSL���L�͂ȃV�X�e���ŗ��p����Ă��邱�Ƃ܂���Ɖe���͏������Ȃ��B���ɒ����x�̐[���x�Ƃ������R�����̖��ɂ��ẮA�Y���@�\�𗘗p���Ă���ꍇ�A���}�ȑΉ������߂���B �@OpenSSL�v���W�F�N�g�́A�e������S���[�U�[�ɑ��āA���₩�ȃA�b�v�f�[�g�̓K�p�������������Ă���B Copyright © ITmedia, Inc. All Rights Reserved.
atmarkit.itmedia.co.jpApr 9, 2026extracted
USN-8155-2: OpenSSL vulnerabilities
Packages openssl - Secure Socket Layer (SSL) cryptographic library and tools openssl1.0 - Secure Socket Layer (SSL) cryptographic library and tools Details USN-8155-1 fixed vulnerabilities in OpenSSL. This update provides the corresponding updates for CVE-2026-28387 for openssl in Ubuntu 20.04 LTS. CVE-2026-28388 for openssl and openssl1.0 in Ubuntu 14.04 LTS, Ubuntu 16.04 LTS, Ubuntu 18.04 LTS, and Ubuntu 20.04 LTS, and CVE-2026-28389 and CVE-2026-28390 for openssl and openssl1.0 for Ubuntu 16.04 LTS, Ubuntu 18.04 LTS, and Ubuntu 20.04 LTS. Original advisory details: Viktor Dukhovni discovered that OpenSSL incorrectly negotiated the expected preferred key exchange group when used as a TLS 1.3 server. This could result in a less preferred key exchange being used, contrary to expectations. This issue only affected Ubuntu 25.10. (CVE-2026-2673) Igor Morgenstern discovered that OpenSSL... USN-8155-1 fixed vulnerabilities in OpenSSL. This update provides the corresponding updates for CVE-2026-28387 for openssl in Ubuntu 20.04 LTS. CVE-2026-28388 for openssl and openssl1.0 in Ubuntu 14.04 LTS, Ubuntu 16.04 LTS, Ubuntu 18.04 LTS, and Ubuntu 20.04 LTS, and CVE-2026-28389 and CVE-2026-28390 for openssl and openssl1.0 for Ubuntu 16.04 LTS, Ubuntu 18.04 LTS, and Ubuntu 20.04 LTS. Original advisory details: Viktor Dukhovni discovered that OpenSSL incorrectly negotiated the expected preferred key exchange group when used as a TLS 1.3 server. This could result in a less preferred key exchange being used, contrary to expectations. This issue only affected Ubuntu 25.10. (CVE-2026-2673) Igor Morgenstern discovered that OpenSSL incorrectly handled certain memory operations when used as a DANE client. A remote attacker could use this issue to cause OpenSSL to crash, resulting in a denial of service, or possibly execute arbitrary code. (CVE-2026-28387) Igor Morgenstern discovered that OpenSSL incorrectly handled certain memory operations when processing a delta CRL. A remote attacker could possibly use this issue to cause OpenSSL to crash, resulting in a denial of service. (CVE-2026-28388) Nathan Sportsman, Daniel Rhea, and Jaeho Nam discovered that OpenSSL incorrectly handled certain memory operations when processing a crafted CMS EnvelopedData message with KeyAgreeRecipientInfo. A remote attacker could possibly use this issue to cause OpenSSL to crash, resulting in a denial of service. (CVE-2026-28389) Muhammad Daffa, Joshua Rogers, and Chanho Kim discovered that OpenSSL incorrectly handled processing of a crafted CMS EnvelopedData message with KeyTransportRecipientInfo. A remote attacker could possibly use this issue to cause OpenSSL to crash, resulting in a denial of service. (CVE-2026-28390) Quoc Tran discovered that OpenSSL incorrectly handled hexadecimal conversion on 32-bit platforms. A remote attacker could use this issue to cause OpenSSL to crash, resulting in a denial of service, or possibly execute arbitrary code. (CVE-2026-31789) Simo Sorce discovered that OpenSSL incorrectly handled failures in RSA KEM RSASVE Encapsulation. A remote attacker could possibly use this issue to obtain sensitive information. (CVE-2026-31790) The problem can be corrected by updating your system to the following package versions: Reduce your security exposure Ubuntu Pro provides ten-year security coverage to 25,000+ packages in Main and Universe repositories, and it is free for up to five machines.
ubuntu.comApr 9, 2026extracted
Data Leakage Vulnerability Patched in OpenSSL
Seven vulnerabilities have been patched with the latest OpenSSL updates, including a flaw that can allow an attacker to obtain sensitive data. The data leakage issue, tracked as CVE-2026-31790 and rated ‘moderate severity’, affects applications that use RSASVE key encapsulation to establish a secret encryption key. The problem is that OpenSSL sometimes fails to properly verify that the encryption succeeded, yet may still return a ‘success’ message, exposing data from an uninitialized memory buffer to the attacker. “The uninitialized buffer might contain sensitive data from the previous execution of the application process, which leads to sensitive data leakage to an attacker,” OpenSSL developers explained in an advisory. The security hole affects versions 3.6, 3.5, 3.4, 3.3, and 3.0. OpenSSL 1.0.2 and 1.1.1 are not impacted. The remaining vulnerabilities have all been classified as ‘low severity’. A majority can be exploited to crash the application and cause a DoS condition. Two of the flaws could in theory lead to arbitrary code execution, but one affects an uncommon configuration of OpenSSL, and one involves sending a specially crafted 1GB X.509 certificate. Updates released by OpenSSL developers in January addressed a dozen vulnerabilities, including a high-severity flaw that could be exploited for remote code execution. High-severity vulnerabilities are now rare in OpenSSL. Only one such vulnerability was found in 2025. Related: High-Severity OpenSSL Vulnerability Found by Apple Allows MitM Attacks Related: RCE Bug Lurked in Apache ActiveMQ Classic for 13 Years Related: OpenSSL Vulnerabilities Allow Private Key Recovery, Code Execution, DoS Attacks Related: Critical Flowise Vulnerability in Attacker Crosshairs
securityweek.comApr 8, 2026extracted
OpenSSL 3.6.2 lands with eight CVE fixes
OpenSSL 3.6.2 lands with eight CVE fixes OpenSSL 3.6.2 patches eight CVEs across a range of components. The project rates the most severe issue in the release as Moderate. What got fixed The release fixes incorrect failure handling in RSA KEM RSASVE encapsulation (CVE-2026-31790) and a loss of key agreement group tuple structure when the DEFAULT keyword is used in server-side configuration of the key-agreement group list (CVE-2026-2673). An out-of-bounds read in AES-CFB-128 on x86-64 CPUs with AVX-512 support (CVE-2026-28386) is also addressed, along with a potential use-after-free in DANE client code (CVE-2026-28387) and a NULL pointer dereference when processing a delta CRL (CVE-2026-28388). Two additional NULL dereference bugs affecting CMS recipient info handling are resolved: one in CMS KeyAgreeRecipientInfo processing (CVE-2026-28389) and one in CMS KeyTransportRecipientInfo processing (CVE-2026-28390). A heap buffer overflow in hexadecimal conversion (CVE-2026-31789) rounds out the security fixes. Regression repairs Beyond the CVEs, the release addresses two behavioral regressions introduced in OpenSSL 3.6.0. One restores the pre-3.6.0 behavior of the X509_V_FLAG_CRL_CHECK_ALL flag. The other fixes a regression in handling stapled OCSP responses that caused handshake failures for OpenSSL 3.6.0 servers with various client implementations. Scope and affected versions OpenSSL 3.6 and 3.5 are vulnerable to several of these issues. OpenSSL 3.4, 3.3, 3.0, 1.0.2, and 1.1.1 are not affected by some of the CVEs patched in this release. Administrators running 3.6.x on x86-64 systems with AVX-512 enabled should prioritize the AES-CFB-128 fix given the memory-read exposure in that path. The 3.6 series carries standard support, with a shorter update window than the long-term support 3.5 branch. Organizations with flexibility in version selection may want to weigh that distinction when planning upgrade schedules.
helpnetsecurity.comApr 8, 2026extracted
The SOC Files: Time to “Sapecar”. Unpacking a new Horabot campaign in Mexico
Introduction In this installment of our SOC Files series, we will walk you through a targeted campaign that our MDR team identified and hunted down a few months ago. It involves a threat known as Horabot, a bundle consisting of an infamous banking Trojan, an email spreader, and a notably complex attack chain. Although previous research has documented Horabot campaigns (here and here), our goal is to highlight how active this threat remains and to share some aspects not covered in those analyses. The starting point As usual, our story begins with an alert that popped up in one of our customers’ environments. The rule that triggered it is generic yet effective at detecting suspicious mshta activity. The case progressed from that initial alert, but fortunately ended on a positive note. Kaspersky Endpoint Security intervened, terminated the malicious process (via a proactive defense module (PDM)) and removed the related files before the threat could progress any further. The incident was then brought up for discussion at one of our weekly meetings. That was enough to spark the curiosity of one of our analysts, who then delved deeper into the tradecraft behind this campaign. The attack chain After some research and a lot of poking around in the adversary infrastructure, our team managed to map out the end-to-end kill chain. In this section, we will break down each stage and explain how the operation unfolds. Stage 1: Initial lure Following the breadcrumbs observed in the reported incident, the activity appears to begin with a standard fake CAPTCHA page. In the incident mentioned above, this page was located at the URL https://evs.grupotuis[.]buzz/0capcha17/ (details about its content can be found here). Similar to the Lumma and Amadey cases, this page instructs the user to open the Run dialog, paste a malicious command into it and then run it. Once deceived, the victim pastes a command similar to the one below: This command retrieved and executed an HTA file that contained the following: It is essentially a small loader. When executed, it opens a blank window, then immediately pulls and runs an external JavaScript payload hosted on the attacker’s domain. The body contains a large block of random, meaningless text that serves purely as filler. Stage 2: A pinch of server-side polymorphism The payload loaded by the HTA file dynamically creates a new element, sets its source to an external VBScript hosted on another attacker-controlled domain, and injects it into the section of a page hardcoded in the HTA. You can see the full content of the page in the box below. Once appended, the external VBScript is immediately fetched and executed, advancing the attack to its next stage. The next-stage VBS content resembles the example shown below. During our analysis, we observed the use of server-side polymorphism because each access to the same resource returned a slightly different version of the code while preserving the same functionality. The script is obfuscated and employs a custom string encoding routine. Below is a more readable version with its strings decoded and replaced using a small Python script that replicates the decode_str() routine. The script performs pretty much the same function as the initial HTA file. It reaches a JavaScript loader that injects and executes another polymorphic VBScript. Unlike the first script, this one is significantly more complex, with more than 400 lines of code. It acts as the heavy lifter of the operation. Below is a brief summary of its key characteristics: Heavy obfuscation: the script uses multiple layers of obfuscation to obscure its behavior. Custom string decoder: employs the same decoding routine found in the first VBScript to reconstruct strings at runtime. Anti-VM and “anti-Avast”: performs basic environment checks and terminates if a specific Avast folder or VM artifacts are detected. Information gathering and exfiltration: collects the host IP, hostname, username, and OS version, then sends this data to a C2 server. Download of additional components: retrieves an AutoIt executable, its compiler (Aut2Exe), a script (au3), and a blob file, placing them under the hardcoded path C:\Users\Public\LAPTOP-0QF0NEUP4 . PowerShell command execution: executes PowerShell commands that reach out to two different URLs (one unavailable and the other leading to the first stager of the spreader, which we describe later in this article). Persistence setup: creates a LNK file and drops it into the Startup folder to maintain persistence. Cleanup routines: removes temporary files and terminates selected processes. During our analysis of the heavy lifter, specifically within the exfiltration routine, we identified where the collected data was being sent. After probing the associated URL and removing the “salvar.php” portion, we uncovered an exposed webpage where the adversary listed all their victims. As you may have noticed, the table is in Brazilian Portuguese and lists victims dating back to May 2025 (this screenshot was taken in September 2025). In the “Localização” (location) column, the adversary even included the victims’ geographic coordinates, which are redacted in the screenshot. A quick breakdown shows that, of the 5384 victims, 5030 were located in Mexico, representing roughly 93% of the total. Stage 3: The evil combination of AutoIT and a banking Trojan It is now time to focus on the files downloaded by our heavy lifter. As previously mentioned, three AutoIT components were dropped on disk: the executable (AutoIT3), the compiler (Aut2Exe), and the script (au3), along with an encrypted blob file. Since we have access to the AutoIt script code, we can analyze its routines. However, it contains over 750 lines of heavily obfuscated code, so let’s focus only on what really matters. The most important routine is responsible for decrypting the blob file (it uses AES-192 with a key derived from the seed value 99521487), loading it directly into memory, and then calling the exported function B080723_N. The decrypted blob is a DLL. We also managed to replicate the decryption logic with a Python script and manually extract the DLL (0x6272EF6AC1DE8FB4BDD4A760BE7BA5ED). After initial triage and basic sandbox execution, we observed the following: The sample is a well-known Delphi banking Trojan detected by several engines under different names, such as Casbaneiro, Ponteiro, Metamorfo, and Zusy. It embeds two old OpenSSL libraries (libeay32.dll and ssleay32.dll) from the Indy Project, an open-source client/server communications library used to establish client/server HTTPS C2 communication. It includes SQL commands used to harvest credentials from browsers. Once loaded into memory, the Trojan sends several HTTP requests to different URLs: Since this malware family has been extensively documented in previous studies, we won’t reiterate its well-known functionality. Instead, we’ll focus on lesser-documented and newly observed features, including the malware’s encryption and protocol handling logic. The sample implements a stateful XOR-subtraction cipher in the sub_00A86B64 subroutine, which is used to protect strings and decrypt HTTP data received from the C2. Unlike simple XOR, each byte of output here depends on both the key and the previous byte. In our sample, the key is the string "0xFF0wx8066h". We can easily reimplement the logic of the routine in Python and integrate the following snippet into our workflow to automate string decryption: Python implementation of the decryption routine The encrypted strings are retrieved in three different ways: through indexed lookups using a global encrypted Delphi string list (also observed by our colleagues at ESET); via direct references to encrypted hex strings in the data section; through indirect references using pointer variables, adding an overhead when automating decryption with scripts. The malware fetches its configuration by performing an HTTPS GET request to the hardcoded, encrypted C2 server. The server responds with a configuration, which is a raw HTTP response, consisting of several values, each individually encrypted with the aforementioned algorithm. The sample extracts specific parameters based on their position in the list. To improve readability, the above screenshot has been edited to include the decrypted parameters, which are separated by double newlines. Configuration retrieval and parsing are initiated in the sub_00AD2C70 subroutine where the first configuration value, the C2 socket connection setting (host;port), is extracted. If parsing fails, the malware falls back to a hardcoded secondary C2 socket address. The socket connection is then established. Additional configuration values are parsed insub_00AD2918 and its subroutines. For example, in the decrypted C2 configuration shown above, parameter 5 contains the “UPON” string that triggers execution, and parameter 6 contains the PowerShell commands that are run when this string is used. Below is the portion of the routine that takes care of parsing this command: In addition to HTTP communication, the malware supports raw socket communication using a custom protocol that encapsulates commands into tags such as or Arg1 Arg2 . The client initiates the C2 connection in sub_00AD331C, where it establishes a TCP socket to the operator’s server and sends the "PRINCIPAL" command to request a control channel. After receiving an OK response, it follows up with an "Info" message containing system details. Once validated, the server replies with a "SocketMain" message containing a session ID, completing the handshake. All subsequent command handling occurs in sub_00AD373C, a central orchestrator routine that parses incoming messages and dispatches the malicious actions. The sample, and therefore the protocol itself, is inherited, from the open-source Delphi Remote Access PC project, as our colleagues at ESET have noted in the past. Below is a visual comparison: Some features from the open-source project, including the chat and file manipulation commands, have been removed, while some mouse-related commands have been renamed with playful prefixes like “LULUZ” (e.g., LULUZLD, LULUZPos). This could be an inside joke, anti-analysis obfuscation, or a way to mark custom variants. Beyond the standard functionality, the protocol now includes a range of additional custom commands, such as LULUZSD for mouse wheel scrolling down, ENTERMANDA to simulate pressing the Enter key, and COLADIFKEYBOARD to inject arbitrary text as keystrokes. The full command set is considerably larger, and while not all commands are implemented in the analyzed sample, evidence of their presence (e.g., in the form of strings) suggests ongoing development. After getting a sense of the protocol, let’s focus on the cipher used. In this sample, traffic exchanged via the C2 socket channel is encrypted using another stateful XOR algorithm with embedded decryption keys. Its logic is implemented in the routines sub_00A9F2D0 (encryption) and sub_00A9F5C0 (decryption): The encryption routine generates three random four-digit integer keys. The first key acts as the initial cipher state, while the other two serve as the multiplier and increment that are applied at every encryption stage to both the state and the data. For each character in the input string, it takes the high byte of the current state, XORs it with the character to encrypt, and then updates the cipher state for the next character. The output is created by prepending the three keys to the ciphertext, encapsulating everything within the “##” markers. The final output looks like this: Here’s a Python snippet to decode such traffic: Although this encryption layer was likely intended to evade network inspection, it ironically makes detection easier due to its highly regular and repetitive structure. This pattern, including the external markers “##”, is uncommon in legitimate traffic and can be used as a reliable network signature for IDS/IPS systems. Below is a Suricata rule that matches the described structure: As documented by our colleagues at Fortinet, the malware contains functionality to display fake pop-ups prompting victims to enter their banking credentials. The images for these pop-ups are stored as encrypted resources. Unlike strings, resources are decrypted using the standard RC4 cipher, and the key pega-avisao3234029284 is retrieved from the previous TStringList structure at offset 3FEh. The wordplay around “pega a visão”, Brazilian slang meaning “get the picture” figuratively, reveals an intentional cultural reference, supporting the already well-known Brazilian ties of the operators who have a native understanding of the language. Below is a collage of pictures where the targeted bank overlays are visible. Stage 4: The spreader In our tests, we noticed that both the VBScript (the heavy lifter) and the Delphi DLL have overlapping functionality for downloading the next stage via PowerShell. Although they rely on different domains, they follow the same URL pattern. We tried accessing URLs meant for downloading the spreader. One returned nothing, while the other displayed a sequence of two PowerShell stagers before reaching the actual spreader. In the second stager, we found several Base64-encoded URLs, but only one of them was active during our analysis. Based on comments found in the spreader code, we suspect that in previous versions or campaigns the spreader was assembled piece by piece from these other URLs. In our case, however, a single URL contained all the necessary code. Yes, we also wondered how PowerShell could possibly accept ASCII chaos as variable/function names, but it does. After cleaning up the messy naming convention and reviewing the well-commented routines (thanks, threat actor), we were able to identify its main duties: Harvest emails via the MAPI namespace; Exfiltrate unique email addresses to the C2; Clean up the outbox; Filter the exfiltrated email addresses against a blocklist of keywords; Prepare a phishing email containing a malicious PDF; Mass-distribute the email to the filtered addresses. One interesting point is that the spreader’s code and comments allow us to extract some useful intel: All comments are written in Brazilian Portuguese, which gives a strong indication of the threat actor’s origin. It is fairly easy to distinguish comments written by a human from those most likely generated by an AI/LLM; the latter are too formal and remarkably well-formatted. One of the human comments actually inspired the title of this article. One of the comments in the code reads “limpa a caixa de saida antes de sapecar”. Sapecar has a very specific meaning that only Brazilian Portuguese speakers would naturally understand. The closest equivalent to this comment in English would be: “Clear the outbox before you blast it off or let it rip.” Our team tracked Horabot activity for a few months and compiled a collection of malicious attachment examples used in this campaign. They are all written in Spanish and urge the user to click a large button in the document to access a “confidential file” or an “invoice”. Clicking the button triggers the same infection chain described in this article. Detection engineering and threat hunting opportunities After navigating this long, layered attack chain, we bet some of the tech folks reading this have already started imagining potential detection opportunities. With that in mind, this section provides some rules and queries that you can use to detect and hunt this threat in your own environment. YARA rules The YARA rules focus on two core components of the operation: the AutoIt script that functions as the loader, and the Delphi DLL that serves as the banking Trojan. Hunting queries You may notice that some patterns in this section do not appear in the URLs described earlier in the article. These additional patterns were included because we observed small variations introduced by the threat actor over time, such as the use of QR codes in the lure pages.
securelist.comMar 18, 2026extracted
ICS Patch Tuesday: Vulnerabilities Fixed by Siemens, Schneider, Moxa, Mitsubishi Electric
Industrial giants Siemens, Schneider Electric, Mitsubishi Electric, and Moxa have published new Patch Tuesday advisories for vulnerabilities found recently in their ICS products. Siemens and Schneider Electric have each published six new advisories. Each of Schneider’s new advisories addresses one vulnerability. The company has informed customers about high-severity issues in EcoStruxure IT Data Center Expert (hardcoded credentials), EcoStruxure Power Monitoring Expert and Power Operation (local arbitrary code execution), and EcoStruxure Automation Expert (command execution and full system compromise). Medium-severity flaws have been patched by the company in Modicon controllers (DoS, account takeover via XSS) and EcoStruxure Foxboro DCS (remote code execution). Siemens has addressed a critical stored XSS vulnerability in Simatic S7-1500 devices, and a potentially severe misconfiguration in Mendix applications. Siemens has also informed customers about vulnerabilities introduced by the use of Fortinet, OpenSSL, and other third-party components. High- and medium-severity issues have been patched by Siemens in the Sicam Siapp SDK, and a low-severity vulnerability has been fixed in Heliox EV chargers. Mitsubishi Electric has published one new advisory to describe a remotely exploitable DoS vulnerability in its Numerical Control Systems, including C80, M800, M800V and M700V series products. Earlier this month the company informed customers about multiple remotely exploitable DoS flaws in MELSEC iQ-F Series controllers. Moxa has published four new advisories, including three describing the impact of vulnerabilities discovered in Intel products. The fourth advisory informs customers that Moxa products are not affected by a recent GNU Inetutils vulnerability. The cybersecurity agency CISA has also published ICS advisories this Patch Tuesday. The advisories inform the public about vulnerabilities in Ceragon Siklu MultiHaul and EtherHaul, Lantronix EDS3000PS and EDS5000, and Apeman cameras. CISA has also published an advisory for a recently disclosed Honeywell building controller vulnerability. The vendor and the researcher who found the flaw have clashed over its impact. Germany’s VDE-CERT has published advisories for Codesys, Janitza, and Weidmueller product vulnerabilities. Some of the Janitza and Weidmueller flaws can be exploited by remote, unauthenticated attackers to fully compromise the targeted system.
securityweek.comMar 11, 2026extracted
OpenAI Rolls Out Codex Security Vulnerability Scanner
OpenAI is rolling out a new AI-powered software vulnerability scanner that the company claims can identify complex issues that other agentic tools may miss. Named Codex Security (formerly Aardvark), the tool is currently in research preview, but it has been tested in private beta since last year, including by major companies such as Netgear. Codex Security is now available to ChatGPT Pro, Enterprise, Business, and Edu customers with free usage for the next month. The AI giant says its new tool is designed to analyze repositories for system context and create a threat model focusing on the system’s role, trusted components, and exposures. Based on the generated threat model, Codex looks for vulnerabilities and rates them by potential real-world impact. It then also proposes patches for the identified flaws. According to OpenAI, Codex Security has been tested against 1.2 million commits over the past 30 days, identifying nearly 800 critical vulnerabilities and more than 10,000 high-severity issues. Vulnerabilities have been found in widely used open source projects such as Chromium, OpenSSL, PHP, GOGS, and GnuTLS. OpenAI’s announcement comes shortly after Claude unveiled its own AI vulnerability scanner, Claude Code Security, which led to the stocks of major cybersecurity companies tumbling. AI-powered vulnerability scanners are not new. GitHub has offered these capabilities for years, and Google claims to have made significant progress in this area. Related: Hackers Weaponize Claude Code in Mexican Government Cyberattack Related: OpenClaw Vulnerability Allowed Websites to Hijack AI Agents Related: Vulnerability in MS-Agent AI Framework Can Allow Full System Compromise
securityweek.comMar 10, 2026extracted
Week in review: Weaponized OAuth redirection logic delivers malware, Patch Tuesday forecast
Week in review: Weaponized OAuth redirection logic delivers malware, Patch Tuesday forecast Here’s an overview of some of last week’s most interesting news, articles, interviews and videos: BlacksmithAI: Open-source AI-powered penetration testing framework BlacksmithAI is an open-source penetration testing framework that uses multiple AI agents to execute different stages of a security assessment lifecycle. BlacksmithAI runs as a hierarchical system in which an orchestrator coordinates task execution across specialized agents. Security debt is becoming a governance issue for CISOs Application security backlogs keep expanding across large development portfolios. Veracode’s 2026 State of Software Security Report puts numbers behind a familiar operational pattern, fixes lag discovery, and older weaknesses stay open across release cycles. Your dependencies are 278 days out of date and your pipelines aren’t protected Applications continue to ship with known weaknesses even as development workflows speed up. A new Datadog State of DevSecOps 2026 report examines how dependency management and pipeline practices are influencing exposure across cloud native environments. AI went from assistant to autonomous actor and security never caught up Enterprise AI deployments have shifted from pilot programs to production systems handling customer data, executing business transactions, and integrating with core infrastructure. That has exposed a significant gap between what AI agents can do and what security teams can observe or control. Cybersecurity is now the price of admission for industrial AI Industrial organizations are accelerating AI deployment across manufacturing, utilities, and transportation and running straight into a security problem. Cisco’s 2026 State of Industrial AI Report, based on responses from more than 1,000 decision-makers across 19 countries, finds that cybersecurity has become the single largest obstacle to AI adoption, outranking skills gaps, integration challenges, and budget constraints. Cybersecurity professionals are burning out on extra hours every week Cybersecurity professionals in the U.S. are working an average of 10.8 extra hours per week beyond their contracted schedules, according to survey data collected from 300 cybersecurity and IT leaders by Sapio Research. That figure effectively adds a sixth working day to the standard week for a large portion of the field. Nearly half of respondents reported working 11 or more overtime hours weekly, and one in five logged more than 16 additional hours. The vulnerability that turns your AI agent against you Zenity Labs disclosed PleaseFix, a family of critical vulnerabilities affecting agentic browsers, including Perplexity Comet, that allow attackers to hijack AI agents, access local files, and steal credentials within authenticated user sessions. The vulnerabilities can be triggered through malicious content embedded in routine workflows, enabling unauthorized actions without user awareness. Threat actors weaponize OAuth redirection logic to deliver malware An ongoing phishing campaign is abusing the OAuth authentication redirection mechanism to avoid triggering conventional email and browser defenses, Microsoft researchers have revealed. The attackers are targeting government and public-sector organizations, and redirecting unsuspecting users from trusted login pages to their own infrastructure, to serve malware or capture login credentials. Coruna: Spy-grade iOS exploit kit powering financial crime A powerful iOS exploit kit has circulated among multiple threat actors over the past year, moving from a commercial surveillance operation to state-linked espionage campaigns and, ultimately, ended into the hands of financially motivated hackers, according to new research from Google’s Threat Intelligence Group (GTIG). Over 1,200 IceWarp servers still vulnerable to unauthenticated RCE flaw (CVE-2025-14500) A critical RCE vulnerability (CVE-2025-14500) in IceWarp, an EU-made business communication and collaboration platform, may be exploited by attackers to gain unauthorized access to exposed unpatched servers. According to the Shadowserver Foundation, there are currently over 1,200 internet-facing instances that have yet to receive a fix, and the organization is sending out alerts to the owners, urging them to update. As AI agents start making purchases, security teams must rethink risk In this Help Net Security interview, Donald Kossmann, CTO at fintech company Chargebacks911, talks about the emerging security, fraud, and governance risks of “agentic commerce,” where AI agents can autonomously make purchasing decisions on behalf of users or organizations. FreeScout vulnerability enables unauthenticated, zero-click RCE via email (CVE-2026-28289) A newly discovered vulnerability (CVE-2026-28289) in the open-source help desk platform FreeScout could allow attackers to take over vulnerable servers by sending a specially crafted email to a FreeScout mailbox. FreeScout is a free, open-source help desk and shared inbox system used by businesses or teams to manage customer support conversations in one place. Cisco warns of SD-WAN Manager exploitation, fixes 48 firewall vulnerabilities Cisco has confirmed that two Catalyst SD-WAN Manager vulnerabilities (CVE-2026-20128 and CVE-2026-20122) patched in late February 2025 are being exploited by attackers. CVE-2026-20128 is a bug in the Data Collection Agent (DCA) feature of Cisco Catalyst SD-WAN Manager, which could allow an authenticated, local attacker to gain DCA user privileges on an affected system. Iran-linked APT targets US critical sectors with new backdoors An Iran-linked hacking group has been active inside the networks of several US organizations since early February, raising concerns that the activity could precede broader cyber operations connected to escalating geopolitical tensions in the Middle East. Why workforce identity is still a vulnerability, and what to do about it Most organizations believe they have workforce identity under control. New hires are verified. Accounts are provisioned. Multi-factor authentication is enforced. Audits are passed. Then a breach happens, often through an account that was “properly secured.” But the problem can be traced back to the fact that identity verification, provisioning, authentication, and recovery operate as separate events, not a continuous system of trust. Engineering trust: A security blueprint for autonomous AI agents AI agents have evolved from just chatbots, answering questions to executing actions using various integrated tools, often autonomously, and as such the traditional security models have become less efficient. A single malicious instruction hidden in a webpage (that the agent processes), can manipulate that agent into performing unintended actions or leaking sensitive data. March 2026 Patch Tuesday forecast: Is AI security an oxymoron? Developers and analysts are using more AI tools to produce code and to test both the performance and security of the finished products. They are also embedding AI functionality in their products directly. But just how secure are these AI tools and routines themselves? Recent reports show they suffer from vulnerabilities just like any other code. When cyber threats start thinking for themselves In this Help Net Security video, Jason Rivera, Field CISO & Head of Solution Engineering at SimSpace, discusses how autonomous AI agents are changing cyber threats. Drawing on experience in the US Army, NSA, Deloitte, and CrowdStrike, he describes how security teams have traditionally measured risk through volume, speed, and sophistication. Why phishing still works today In this Help Net Security video, Gal Livschitz, Senior Penetration Tester at Terra Security, explains how phishing has evolved and why employees still fall for it. He outlines how phishing now uses HTTPS, branded pages, and lookalike domains, making attacks harder to spot. He highlights communication overload as a key weakness that attackers exploit. Motorola turns to GrapheneOS for smartphone security upgrade Motorola is strengthening smartphone security through a long-term partnership with the GrapheneOS Foundation, a mobile security nonprofit that develops a hardened operating system based on the Android Open Source Project. Anthropic’s Claude hit by widespread service outage (updated) Anthropic suffered widespread service disruptions Monday morning, leaving thousands of users unable to access its Claude AI platform. Most users reporting problems said they encountered errors when attempting to log in. Meta AI in WhatsApp organizes chats and reopens privacy issues The trend of integrating AI into digital platforms continues. In the latest Android beta release (2.26.9.4), the company has introduced a feature that allows users to organize their chat history with the help of Meta AI. Anthropic poaches users from rival chatbots with easier migration The controversy over Anthropic’s negotiations with the Pentagon has driven increased interest in Claude. Negotiations between the Department of Defense and Anthropic collapsed after a deadline for an agreement expired without a deal. The Pentagon had pressed the company to loosen certain restrictions on how its AI systems could be used. Anthropic declined and kept its existing policy limits in place. $100 radio equipment can track cars through their tire sensors When people consider what might track their movements, they think of smartphone apps, GPS services, or roadside cameras. The tires of a new car rarely enter that equation. Researchers at IMDEA Networks Institute, together with European partners, found that Tire Pressure Monitoring System (TPMS) sensors inside each wheel broadcast unencrypted wireless signals containing persistent identifiers. Google speeds up Chrome updates with new security-focused release cycle The Chrome browser is moving to a two-week release cycle, a change intended to give developers and users faster access to new features, performance improvements and bug fixes. The new schedule begins with the stable release of Chrome 153 on September 8, 2026, followed by new beta and stable releases every two weeks. The change applies to desktop, Android and iOS platforms, while the Dev and Canary channels remain unchanged. Workers reviewing Meta Ray-Ban footage encounter users’ intimate moments Bank details and intimate moments captured without people realizing they are being recorded are the new privacy nightmare behind the latest tech fashion hit, Meta Ray-Ban smart glasses. A joint investigation by Svenska Dagbladet and Göteborgs-Posten found that footage and audio recorded by Meta’s Ray-Ban smart glasses are reviewed by human contractors in Kenya, including recordings containing sensitive personal material. Authorities pull plug on Tycoon 2FA phishing-as-a-service platform Tycoon 2FA, a phishing-as-a-service platform that allowed cybercriminals to bypass MFA and break into online accounts, has been disrupted by law enforcement agencies and cybersecurity partners. Western governments lay the groundwork for secure 6G networks Governments are preparing for 6G, the next generation of mobile networks, placing security and resilience among their top priorities. In response, seven countries participating in the Global Coalition on Telecoms (GCOT) have introduced a set of 6G Security and Resilience Principles, developed with support from industry partners. Backup strategies are working, and ransomware gangs are responding with data theft Business email compromise (BEC) and funds transfer fraud combined for 58% of all cyber insurance claims filed in 2025, according to data from Coalition covering more than 100,000 policyholders across the United States, Canada, the United Kingdom, Australia, and Germany. OpenAI’s GPT-5.4 doubles down on safety as competition heats up In the midst of recent developments and controversies surrounding a contract with the U.S. Department of Defense, OpenAI released the GPT-5.4 model. The release comes at a time when users are reportedly leaving ChatGPT for rival chatbots, particularly Anthropic’s Claude. Microsoft working on Teams feature to keep unauthorized bots at bay Microsoft plans to add a new Teams feature that lets meeting admins identify and control third-party bots before they join. According to the Microsoft 365 Roadmap, the feature is scheduled to begin rolling out in May 2026 on Desktop, Mac, Linux, iOS, and Android versions of Microsoft Teams. AI risk moves into the security budget spotlight Enterprises are pushing AI deeper into workflows that touch sensitive data across cloud platforms and SaaS apps. The 2026 Thales Data Threat Report, based on a survey of 3,120 respondents in 20 countries, places that shift alongside growing pressure on data protection, identity controls, and cloud security. UK reduces cyberattack fix times from two months to eight days The UK government has launched a new vulnerability monitoring service (VMS) that promises to reduce the time needed to fix critical cyber weaknesses across the public sector. The service, launched as part of the Blueprint for Modern Digital Government, published in January 2025, continuously scans internet-facing systems at around 6,000 public sector organizations. Using commercial and proprietary tools, it detects about 1,000 types of cyber vulnerabilities. IPFire ships its 200th core update with a new domain blocklist and kernel upgrade Network firewall distribution IPFire released Core Update 200, marking the 200th incremental update to the 2.29 branch. The release bundles a kernel upgrade, a beta domain blocklist service, security patches for OpenSSL and glibc, and a range of component updates. 5 years of shifting cybersecurity behavior Online security is built through routine decisions made across devices and accounts. People choose how to create passwords, how often to reuse them, and how much effort to invest in protecting personal data. The National Cybersecurity Alliance and CybSafe’s Oh, Behave! The Cybersecurity Attitudes and Behaviors Report: 2021–2025 follows those patterns over five years, drawing on responses from more than 24,000 adults and documenting how attitudes and behaviors shift over time. Healthcare organizations are accepting cyber risk to cut costs Healthcare organizations are cutting cybersecurity budgets under financial pressure even as the threats targeting their systems intensify. A PwC survey of 381 global healthcare executives, conducted between May and July 2025, puts numbers to the gap between the risks the sector faces and the controls it has in place. Android’s March 2026 security patch fixes over 100 flaws, one under targeted exploitation The Android March 2026 security patch addresses vulnerabilities across dozens of components and includes one CVE confirmed under active exploitation. Devices running a patch level of 2026-03-05 or later receive fixes for all disclosed issues. New Defender deployment tool streamlines Windows device onboarding with single executable Microsoft’s Defender deployment tool for Windows helps administrators manage device onboarding at scale with updated progress visibility and additional controls. Cloudflare tracked 230 billion daily threats and here is what it found Cloudflare’s network blocks over 230 billion threats per day. The volume indicates how routine and automated the attack cycle has become, and the patterns behind that volume point to a shift in how breaches begin and progress. Cloudflare’s threat research unit, Cloudforce One, published its inaugural cyber threat report 2026, covering activity observed through 2025 and projecting into the year ahead. The report draws on telemetry from Cloudflare’s network, which handles roughly 20% of global web traffic. Immutable Linux distribution Nitrux 6.0.0 adds GPU passthrough, boot-level recovery, C++ update system Nitrux 6.0.0, released March 3, 2026, packages several components that security practitioners running Linux workstations will find worth examining: a new hypervisor orchestrator with IOMMU-enforced isolation, a rewritten update system with cryptographic verification, and a recovery mechanism that operates from within the boot process itself. LeakBase cybercrime forum with 142,000 users taken down in global operation LeakBase, an open-web cybercrime forum facilitating the trade of leaked databases and “stealer logs” containing stolen credentials, has been taken down in an international law enforcement operation coordinated by Europol and involving authorities from 14 countries. Google changes Play Store policies after settling Epic Games dispute Google is making changes to the Play Store after settling its legal fight with Epic Games, focusing on three areas: more billing options, lower fees with new programs for developers, and a program for registered app stores. That attractive online ad might be a malware trap Malware increasingly travels through the infrastructure that delivers online advertising. The Media Trust’s Global Report on Digital Trust, Ad Integrity, and the Protection of People describes a digital ad ecosystem where scam campaigns, malicious redirects, and malware delivery appear alongside marketing traffic. What happens when AI teams compete against human hackers A cybersecurity competition produced what may be the largest controlled dataset comparing AI-augmented teams to human-only teams on professional-grade offensive security tasks. The event, called NeuroGrid, ran for 72 hours on the Hack The Box platform and drew 1,337 registered human-only teams and 156 registered AI-agent teams competing across 36 challenges in nine security domains at four difficulty levels. Cursor Automations turns code review and ops into background tasks Cursor Automations, the always-on agent platform from Cursor, is expanding with a new generation of autonomous systems that streamline code review, incident response, and other engineering workflows. The platform runs AI agents on schedules or in response to development events. New cyber module strengthens risk planning for health organizations The Administration for Strategic Preparedness and Response’s (ASPR) new cybersecurity module in the Risk Identification and Site Criticality (RISC) 2.0 Toolkit helps organizations identify critical gaps, prioritize investments, and make informed decisions about risk mitigation to reduce disruptions to patient care and strengthen resilience. Secure by Design: Building security in at the beginning Secure by Design is not a single tool, product, or one‑time activity. It is a holistic approach that requires security to be deliberately embedded from the very beginning, at the point where systems, software, and services are conceived and designed. Rather than reacting to vulnerabilities after deployment, Secure by Design emphasizes anticipating risk early and addressing it through intentional design decisions, clearly defined security requirements, and accountability across the entire lifecycle. Webinar: The True State of Security 2026 In the webinar The True State of Security 2026, you’ll gain insight into why AI is distracting teams from more persistent risks and how human access and permissions remain the weakest link. You’ll also learn why current security workflows are slowing organizational growth and what a balanced security strategy should look like heading into 2026. Cybersecurity jobs available right now: March 3, 2026 We’ve scoured the market to bring you a selection of roles that span various skill levels within the cybersecurity field. Check out this weekly selection of cybersecurity jobs available right now. New infosec products of the week: March 6, 2026 Here’s a look at the most interesting products from the past week, featuring releases from Beazley Security, Push Security, Samsung, and Tufin.
helpnetsecurity.comMar 8, 2026extracted
IPFire ships its 200th core update with a new domain blocklist and kernel upgrade
IPFire ships its 200th core update with a new domain blocklist and kernel upgrade Network firewall distribution IPFire released Core Update 200, marking the 200th incremental update to the 2.29 branch. The release bundles a kernel upgrade, a beta domain blocklist service, security patches for OpenSSL and glibc, and a range of component updates. The kernel has been rebased on Linux 6.18.7 LTS, bringing updated hardware security mitigations alongside network throughput and latency improvements. Linux developers deprecated ReiserFS support in this kernel line, and IPFire installations running on that filesystem cannot apply the update without first reinstalling on a supported filesystem. IPFire DBL enters beta The release introduces IPFire DBL, a domain blocklist the project is building to replace the retired Shalla list, which the web proxy previously relied on to filter malware, social networking, and adult content. DBL is available in two places: the URL filter for proxy-based blocking, and as a Suricata rules source. When used with Suricata, the blocklist enables deep packet inspection across DNS, TLS, HTTP, and QUIC connections. The project describes DBL as an early beta and is soliciting community feedback. A DNS Firewall with native content filtering is listed on the roadmap as the next major milestone. Suricata and IPS changes A cache management fix addresses a bug introduced in the previous update, where Suricata’s pre-compiled signature cache grew without limit and consumed disk space. A backported patch now causes Suricata to clean up unused signatures automatically. The Suricata reporter has been updated to surface hostname information and additional protocol metadata for alerts involving DNS, HTTP, TLS, and QUIC connections. That data will appear in alert emails and PDF reports, giving administrators more context when investigating policy violations. OpenVPN configuration updates Several OpenVPN client configuration behaviors have changed. MTU values will now be pushed from the server rather than baked into client configs, giving administrators flexibility to adjust the value after deployment. The OTP authentication token will also be pushed server-side when OTP is enabled. The CA certificate has been removed from client configuration files because it is already contained in the PKCS12 container; its presence was causing import failures in NetworkManager on the command line. DNS proxy goes multi-threaded Unbound, the DNS proxy component, will now launch one thread per CPU core. Previously it ran on a single thread. The change is expected to reduce response times under load. Wireless access point fixes Support for 802.11a/g has been restored after being dropped unintentionally in a prior release. A separate fix prevents hostapd from flooding logs with debug output when debugging is enabled. PSK values containing special characters are now accepted. Security patches OpenSSL has been updated to version 3.6.1, patching twelve CVEs: CVE-2025-11187, CVE-2025-15467, CVE-2025-15468, CVE-2025-15469, CVE-2025-66199, CVE-2025-68160, CVE-2025-69418, CVE-2025-69419, CVE-2025-69420, CVE-2025-69421, CVE-2026-22795, and CVE-2026-22796. The glibc library received patches for CVE-2026-0861, CVE-2026-0915, and CVE-2025-15281. Package updates Notable component versions in this release include Apache 2.4.66, BIND 9.20.18, cURL 8.18.0, OpenVPN 2.6.17, strongSwan 6.0.4, Suricata 8.0.3, Unbound 1.24.2, ClamAV 1.5.1, Samba 4.23.4, and Tor 0.4.8.21. Must read: 40 open-source tools redefining how security teams secure the stack Firmware scanning time, cost, and where teams run EMBA Subscribe to the Help Net Security ad-free monthly newsletter to stay informed on the essential open-source cybersecurity tools. Subscribe here!
helpnetsecurity.comMar 2, 2026extracted
L’ATP russo che sfrutta una vulnerabilità di Office è la nuova normalità
Una ricerca svolta dall’azienda americana di cyber security Trellix ha dimostrato che il collettivo filorusso ATP28 è stato capace di lanciare una sofisticata operazione di cyber spionaggio trasformando – in meno di 24 ore dalla sua divulgazione – una vulnerabilità di Microsoft Office in un’arma affilata. Il gruppo APT28, conosciuto anche con il nome di Fancy Bear e collegato all’intelligence militare russa, è già noto per la distribuzione di malware e ora sembra avere fatto un passo avanti per capacità e rapidità. Infatti, due delle peculiarità di questo nuovo attacco, sono le doti organizzative del collettivo e la velocità con cui ha sferrato l’offensiva contro infrastrutture critiche e istituzioni governative in diversi Paesi. Fulcro dell’attacco è la vulnerabilità CVE-2026-21509, che permette di aggirare le restrizioni di sicurezza di Office relative agli oggetti OLE (Object Linking and Embedding). Sfruttando questo bug, i documenti malevoli attivano l’esecuzione automatica di codice nel momento stesso in cui vengono aperti, senza richiedere l’attivazione di macro o altre interazioni da parte dell’utente. L’exploit utilizza il protocollo WebDAV per contattare server remoti sotto il controllo degli attaccanti e scaricare i componenti successivi della catena di infezione. Indice degli argomenti Breve analisi tecnica della vulnerabilità di Office Un esempio magistrale di targeting e di ingegneria sociale: l’operazione si è concentrata in un arco temporale di 72 ore, tra il 28 e il 30 gennaio 2026, colpendo organizzazioni in nove paesi dell’Europa orientale e dell’area mediterranea, tra i quali Polonia, Slovenia, Grecia, Turchia, Ucraina e Emirati Arabi Uniti. Le vittime sono state selezionate con estrema precisione: il 40% dei target riguarda ministeri della Difesa, seguiti da operatori di trasporto e logistica (35%) e rappresentanze diplomatiche. Per indurre le vittime ad aprire i file, APT28 ha utilizzato account email governativi reali ma precedentemente compromessi in Romania, Bolivia e Ucraina. Le esche utilizzate sfruttavano temi di attualità geopolitica, come allerte sul contrabbando di armi dalla Siria (45% delle email), inviti a programmi di addestramento militare (25%) e bollettini di emergenza meteorologica (10%). L’attacco si sviluppa attraverso diversi stadi per massimizzare l’elusione delle difese. Il primo stadio prevede il download di un collegamento LNK e di una DLL denominata SimpleLoader che usa tre diversi schemi di cifratura XOR, inclusa una chiave a rotazione di 76 caratteri, per proteggere i propri componenti interni e i payload. Una volta eseguito, SimpleLoader stabilisce la persistenza sul sistema attraverso il dirottamento di oggetti COM e la creazione di un’attività pianificata temporanea chiamata OneDriveHealth. L’infezione procede poi con due varianti. Una di queste usa uno steganography loader (EhStoreShell.dll) che elabora un file PNG apparentemente innocuo per poi eseguire codice fileless. La seconda variante, NotDoor, è una backdoor specifica per Microsoft Outlook progettata per la raccolta di intelligence a lungo termine. NotDoor modifica il registro di sistema per disabilitare i controlli di sicurezza delle macro di Outlook e installa un file VbaProject.OTM. Questo componente inoltra automaticamente ogni email in entrata e i dati delle cartelle principali (Posta in arrivo, Bozze, Posta indesiderata) a indirizzi email controllati dagli attaccanti. Sono sempre i soliti ma con una variante. Le organizzazioni devono applicare le patch urgenti rilasciate dai fornitori di software e hardware a ritmi serrati. Del resto, essendo urgenti, richiedono una reazione più che pronta da parte di chi amministra i sistemi aziendali. Il controllo e la riduzione delle superfici d’attacco è sempre più fondamentale, e ciò rimanda alla filosofia Zero Trust, alle tecniche di Identity and Access Management (IAM) ed Endpoint Detection and Response (EDR), per citare le più diffuse. Inoltre, dotarsi di sistemi per il monitoraggio delle attività di rete e, nello specifico, delle comunicazioni non autorizzate verso servizi di cloud storage, è un’ottima tecnica. La prevenzione rimane fondamentale, perché questo ATP dimostra che anche personale esperto può cadere nella trappola. Una domanda a cui l’ICT Security Manager Enrico Morisi dà risposta, esponendo anche le peculiarità delle minacce AI-driven. “Una delle caratteristiche peculiari delle cosiddette minacce AI-driven è certamente la velocità, che si manifesta, per esempio, in termini di capacità di evolvere, di analizzare, di scoprire, di sfruttare, di orchestrare e di colpire. In particolare, l’attitudine della AI a scoprire nuove vulnerabilità, gli zero-day, sta cambiando la cybersecurity, così come la conosciamo, più velocemente di quanto ci si aspetti. Si pensi, ad esempio, alla recente individuazione di 12 nuovi zero-day in OpenSSL vulnerabilità tutt’altro che insignificanti, fornendo in ben 5 casi anche una soluzione appropriata di remediation (patch) a dimostrazione che la rivoluzione in corso impatta in modo rilevante sia sulle capacità offensive sia, fortunatamente, su quelle difensive. L’accelerazione che contraddistingue i processi di scoperta di nuove vulnerabilità e il loro sfruttamento in attacchi reali, da un lato, e le carenze che spesso si riscontrano nei processi di vulnerability management implementati dalle organizzazioni, dall’altro, costituiscono una miscela esplosiva, dove il fattore tempo diviene determinante, consentendo agli attaccanti di adottare anche TTPs sempre più sofisticate, soprattutto in termini di evasion, obfuscation e persistence. Il tutto si complica enormemente nel caso in cui, peraltro sempre più frequente, occorra gestire un paniere di vulnerabilità critiche simultanee, in prodotti differenti, di fornitori differenti: il modello ‘reattivo’ di manutenzione programmata diviene insostenibile e, semplicemente, ‘crolla’, trasformandosi in gestione emergenziale. È evidente che occorra un cambio di approccio, caratterizzato innanzitutto dall’adozione di ulteriori misure di mitigazione del rischio come, per esempio, la riduzione della superficie d’attacco, in particolare con riferimento al volume e alla tipologia di dispositivi ‘edge’ introdotti, ma anche da una inevitabile prioritizzazione delle attività di “patching”, sulla base del rischio reale, vale a dire della effettiva sfruttabilità e del contesto dell’organizzazione, e non solo di quello teorico, affiancando scoring system come l’EPSS (di FIRST) il KEV (di CISA) e l’SSVC (di CISA e Carnegie Mellon University SEI) al più noto CVSS, oltre che, soprattutto, dal potenziamento di servizi essenziali come il SOC, e delle tecnologie a supporto, con opportune soluzioni di AI”. In conclusione, la crescente complessità delle architetture di rete e la crescente sofisticatezza delle tecniche adottate dagli attaccanti, insieme, danno vita a una “nuova normalità”, nei cui perimetri le minacce – soprattutto quelle che fanno leva sulle AI – diventano più rapide, repentine ed efficaci.
cybersecurity360.itFeb 26, 2026extracted
ThreatsDay Bulletin: OpenSSL RCE, Foxit 0-Days, Copilot Leak, AI Password Flaws & 20+ Stories
The cyber threat space doesn’t pause, and this week makes that clear. New risks, new tactics, and new security gaps are showing up across platforms, tools, and industries — often all at the same time. Some developments are headline-level. Others sit in the background but carry long-term impact. Together, they shape how defenders need to think about exposure, response, and preparedness right now. This edition of ThreatsDay Bulletin brings those signals into one place. Scan through the roundup for quick, clear updates on what’s unfolding across the cybersecurity and hacking landscape. Privacy model hardeningGoogle announced the first beta version of Android 17, with two privacy and security enhancements: the deprecation of Cleartext Traffic Attribute and support for HPKE Hybrid Cryptography to enable secure communication using a combination of public key and symmetric encryption (AEAD). "If your app targets (Android 17) or higher and relies on usesCleartextTraffic='true' without a corresponding Network Security Configuration, it will default to disallowing cleartext traffic," Google said. "You are encouraged to migrate to Network Security Configuration files for granular control." RaaS expands cross-platform reachA new analysis of the LockBit 5.0 ransomware has revealed that the Windows version packs in various defense evasion and anti-analysis techniques, including packing, DLL unhooking, process hollowing, patching Event Tracing for Windows (ETW) functions, and log clearing. "What's notable among the multiple systems support is its proclaimed capability to 'work on all versions of Proxmox,'" Acronis said. "Proxmox is an open-source virtualization platform and is being adopted by enterprises as an alternative to commercial hypervisors, which makes it another prime target of ransomware attacks." The latest version also introduces dedicated builds tailored for enterprise environments, highlighting the continued evolution of ransomware-as-a-service (RaaS) operations. Mac users lured via nested obfuscationCybersecurity researchers have detailed a new evolution of the ClickFix social engineering tactic targeting macOS users. "Dubbed Matryoshka due to its nested obfuscation layers, this variant uses a fake installation/fix flow to trick victims into executing a malicious Terminal command," Intego said. "While the ClickFix tactic is not new, this campaign introduces stronger evasion techniques — including an in-memory, compressed wrapper and API-gated network communications — designed to hinder static analysis and automated sandboxes." The campaign primarily targets users attempting to visit software review sites, leveraging typosquatting in the URL name to redirect them to fake sites and activate the infection chain. Loader pipeline drives rapid domain takeoverAnother new ClickFix campaign detected in February 2026 has been observed delivering a malware-as-a-service (MaaS) loader known as Matanbuchus 3.0. Huntress, which dissected the attack chain, said the ultimate objective of the intrusion was to deploy ransomware or exfiltrate data based on the fact that the threat actor rapidly progressed from initial access to lateral movement to domain controllers via PsExec, rogue account creation, and Microsoft Defender exclusion staging. The attack also led to the deployment of a custom implant dubbed AstarionRAT that supports 24 commands to facilitate credential theft, SOCKS5 proxy, port scanning, reflective code loading, and shell execution. According to data from the cybersecurity company, ClickFix fueled 53% of all malware loader activity in 2025. Typosquat chain targets macOS credentialsIn yet another ClickFix campaign, threat actors are relying on the "reliable trick" to host malicious instructions on fake websites disguised as Homebrew ("homabrews[.]org") to trick users into pasting them on the Terminal app under the pretext of installing the macOS package manager. In the attack chain documented by Hunt.io, the commands in the typosquatted Homebrew domain are used to deliver a credential-harvesting loader and a second-stage macOS infostealer dubbed Cuckoo Stealer. "The injected installer looped on password prompts using 'dscl . -authonly,' ensuring the attacker obtained working credentials before deploying the second stage," Hunt.io said. "Cuckoo Stealer is a full-featured macOS infostealer and RAT: It establishes LaunchAgent persistence, removes quarantine attributes, and maintains encrypted HTTPS command-and-control communications. It collects browser credentials, session tokens, macOS Keychain data, Apple Notes, messaging sessions, VPN and FTP configurations, and over 20 cryptocurrency wallet applications." The use of "dscl . -authonly" has been previously observed in attacks deploying Atomic Stealer. Phobos affiliate detained in EuropeAuthorities from Poland's Central Bureau for Combating Cybercrime (CBZC) have detained a 47-year-old man over suspected ties to the Phobos ransomware group. He faces a potential prison sentence of up to five years. The CBZC said the "47-year-old used encrypted messaging to contact the Phobos criminal group, known for conducting ransomware attacks," adding the suspect's devices contained logins, passwords, credit card numbers, and server IP addresses that could have been used to launch "various attacks, including ransomware." The arrest is part of Europol's Operation Aether, which targets the 8Base ransomware group, believed to be linked to Phobos. It has been almost exactly a year since international law enforcement dismantled the 8Base crew. More than 1,000 organizations around the world have been targeted in Phobos ransomware attacks, and the cybercriminals are believed to have obtained over $16 million in ransom payments. Industrial ransomware surge acceleratesThere has been a sharp rise in the number of ransomware groups targeting industrial organizations as cybercriminals continue to exploit vulnerabilities in operational technology (OT) and industrial control systems (ICS), Dragos warned. A total of 119 ransomware groups targeting industrial organizations were tracked during 2025, a 49% increase from the 80 tracked in 2024. 2025 saw 3,300 industrial organizations around the world hit by ransomware, compared with 1693 in 2024. The most targeted sector was manufacturing, followed by transportation. In addition, a hacking group tracked as Pyroxene has been observed conducting "supply chain-leveraged attacks targeting defense, critical infrastructure, and industrial sectors, with operations expanding from the Middle East into North America and Western Europe." It often leverages initial access provided by PARISITE, to enable movement from IT into OT networks. Pyroxene overlaps with activity attributed to Imperial Kitten (aka APT35), a threat actor affiliated with the cyber arm of the Islamic Revolutionary Guard Corps (IRGC). Copilot bypassed DLP safeguardsMicrosoft confirmed a bug (CW1226324) that let Microsoft 365 Copilot summarize confidential emails from Sent Items and Drafts folders since January 21, 2026, without users' permission, bypassing data loss prevention (DLP) policies put in place to safeguard sensitive data. A fix was deployed by the company on February 3, 2026. However, the company did not disclose how many users or organizations were affected. "Users' email messages with a confidential label applied are being incorrectly processed by Microsoft 365 Copilot chat," Microsoft said. "The Microsoft 365 Copilot 'work tab' Chat is summarizing email messages even though these email messages have a sensitivity label applied, and a DLP policy is configured. A code issue is allowing items in the sent items and draft folders to be picked up by Copilot even though confidential labels are set in place." (Update: As of February 19, 2026, Microsoft said the root cause of this issue has been addressed for most customers, and that it's now "completing a longer-term, comprehensive sync to apply this fix retroactively to previously affected messages within the Sent and Draft folders to fully remediate the impact.") Jira trials weaponized for spamThreat actors are abusing the trust and reputation associated with Atlassian Jira Cloud and its connected email system to run automated spam campaigns and bypass traditional email security. To accomplish this, the operators created Atlassian Cloud trial accounts using randomized naming conventions, allowing them to generate disposable Jira Cloud instances at scale. "Emails were tailored to target specific language groups, targeting English, French, German, Italian, Portuguese, and Russian speakers — including highly skilled Russian professionals living abroad," Trend Micro said. "These campaigns not only distributed generic spam, but also specifically targeted sectors such as government and corporate entities." The attacks, active from late December 2025 through late January 2026, primarily targeted organizations using Atlassian Jira. The goal was to get recipients to open the emails and click on malicious links, which would initiate a redirect chain powered by the Keitaro Traffic Distribution System (TDS) and then finally lead them to pages peddling investment scams and online casino landing sites, suggesting that financial gain was likely the main objective. GitLab SSRF now federally mandated patchThe U.S. Cybersecurity and Infrastructure Security Agency (CISA), on February 18, 2026, added CVE-2021-22175 to its Known Exploited Vulnerabilities (KEV) catalog, requiring Federal Civilian Executive Branch (FCEB) agencies to apply the patch by March 11, 2026. "GitLab contains a server-side request forgery (SSRF) vulnerability when requests to the internal network for webhooks are enabled," CISA said. In March 2025, GreyNoise revealed that a cluster of about 400 IP addresses was actively exploiting multiple SSRF vulnerabilities, including CVE-2021-22175, to target susceptible instances in the U.S., Germany, Singapore, India, Lithuania, and Japan. Telegram bots fuel Fortune 500 phishingAn elusive, financially motivated threat actor dubbed GS7 has been targeting Fortune 500 companies in a new phishing campaign that leverages trusted company branding with lookalike websites aimed at harvesting credentials via Telegram bots. The campaign, codenamed Operation DoppelBrand, targets top financial institutions, including Wells Fargo, USAA, Navy Federal Credit Union, Fidelity Investments, and Citibank, as well as technology, healthcare, and telecommunications firms worldwide. Victims are lured through phishing emails and redirected to counterfeit pages where credentials are harvested and transmitted to Telegram bots controlled by the attacker. According to SOCRadar, the group itself, however, has a history stretching back to 2022. The threat actor is said to have registered more than 150 malicious domains in recent months using registrars such as NameCheap and OwnRegistrar, and routing traffic through Cloudflare to evade detection. GS7's end goals include not only harvesting credentials, but also downloading remote management and monitoring (RMM) tools like LogMeIn Resolve on victim systems to enable remote access or the deployment of malware. This has raised the possibility that the group may even act as an initial access broker (IAB), selling the access to ransomware groups or other affiliates. Remcos shifts to live C2 surveillancePhishing emails disguised as invoices, job offers, or government notices are being used to distribute a new variant of Remcos RAT to facilitate comprehensive surveillance and control over infected systems. "The latest Remcos variant has been observed exhibiting a significant change in behaviour compared to previous versions," Point Wild said. "Instead of stealing and storing data locally on the infected system, this variant establishes direct online command-and-control (C2) communication, enabling real-time access and control. In particular, it leverages the webcam to capture live video streams, allowing attackers to monitor targets remotely. This shift from local data exfiltration to live, online surveillance represents an evolution in Remcos’ capabilities, increasing the risk of immediate espionage and persistent monitoring." China-made vehicles restricted on basesPoland's Ministry of Defence has banned Chinese cars, and other motor vehicles equipped with technology to record position, images, or sound, from entering protected military facilities due to national security concerns and to "limit the risk of access to sensitive data." The ban also extends to connecting work phones to infotainment systems in motor vehicles produced in China. The ban isn't permanent: the Defence Ministry has called for the development of a vetting process to allow carmakers to undergo a security assessment that, if passed, can allow their vehicles to enter protected facilities. "Modern vehicles equipped with advanced communication systems and sensors can collect and transmit data, so their presence in protected zones requires appropriate safety regulations," the Polish Army said. The measures introduced are preventive and comply with the practices of NATO countries and other allies to ensure the highest standards of defense infrastructure protection. They are part of a wider process of adapting security procedures to the changing technological environment and current requirements for the protection of critical infrastructure." DKIM replay fuels invoice scamsBad actors are abusing legitimate invoices and dispute notifications from trusted vendors, such as PayPal, Apple, DocuSign, and Dropbox Sign (formerly HelloSign), to bypass email security controls. "These platforms often allow users to enter a 'seller name' or add a custom note when creating an invoice or notification," Casey-owned INKY said. "Attackers abuse this functionality by inserting scam instructions and a phone number into those user-controlled fields. They then send the resulting invoice or dispute notice to an email address they control, ensuring the malicious content is embedded in a legitimate, vendor-generated message." Because these emails originate from a legitimate company, they bypass checks like Domain-based Message Authentication, Reporting and Conformance (DMARC). As soon as the legitimate email is received, the attacker proceeds to forward it to the intended targets, allowing the "authentic looking" message to land in the victims' inboxes. The attack is known as a DKIM replay attack. RMM abuse surges 277%A new report from Huntress has revealed that the abuse of Remote Monitoring and Management (RMM) software surged 277% year-over-year, accounting for 24% of all observed incidents. Threat actors have begun to increasingly favor these tools because they are ubiquitous in enterprise environments, and the trusted nature of the RMM software allows malicious activity to blend in with legitimate usage, making detection harder for defenders. They also offer increased stealth, persistence, and operational efficiency. "As cybercriminals built entire playbooks around these legitimate, trusted tools to drop malware, steal credentials, and execute commands, the use of traditional hacking tools plummeted by 53%, while remote access trojans and malicious scripts dropped by 20% and 11.7%, respectively," the company said. Texas targets China-linked tech firmsTexas Attorney General Ken Paxton has sued TP-Link for "deceptively marketing its networking devices and allowing the Chinese Communist Party ('CCP') to access American consumers' devices in their homes." Paxton's lawsuit alleges that TP Link's products have been used by Chinese hacking groups to launch cyber attacks against the U.S. and that the company is subject to Chinese data laws, which it said require firms operating in the country to support its intelligence services by "divulging Americans' data." TP-Link told The Record that these allegations are "without merit" and that neither the Chinese government nor the Chinese Communist Party (CCP) exercises control over the company, its products, or user data. It also added that all U.S. user data is stored on domestic Amazon Web Services (AWS) servers. In a second lawsuit, Paxton also accused Anzu Robotics of misleading Texas consumers about the "origin, data practices, and security risks of its drones." Paxton's office described the company's products as "21st century Trojan horse linked to the CCP." MetaMask backdoor expands DPRK campaignThe North Korea-linked campaign known as Contagious Interview is designed to target IT professionals working in cryptocurrency, Web3, and artificial intelligence sectors to steal sensitive data and financial information using malware such as BeaverTail and InvisibleFerret. However, recent iterations of the campaign have expanded their data theft capabilities by tampering with the MetaMask wallet extension (if it's installed) through a lightweight JavaScript backdoor that shares the same functionality as InvisibleFerret, according to security researcher Seongsu Park. "Through the backdoor, attackers instruct the infected system to download and install a fake version of the popular MetaMask cryptocurrency wallet extension, complete with a dynamically generated configuration file that makes it appear legitimate," Park said. "Once installed, the compromised MetaMask extension silently captures the victim's wallet unlock password and transmits it to the attackers’ command-and-control server, giving them complete access to cryptocurrency funds." Booking.com kits hit hotels, guestsBridewell has warned of a resurgence in malicious activity targeting the hotel and retail sector. "The primary motivation driving this incident is financial fraud, targeting two victims: hotel businesses and hotel customers, in sequential order," security researcher Joshua Penny said. "The threat actor(s) utilize impersonation of the Booking.com platform through two distinct phishing kits dedicated to harvesting credentials and banking information from each victim, respectively." It's worth noting that the activity shares overlap with a prior activity wave disclosed by Sekoia in November 2025, although the use of a dedicated phishing kit is a new approach by either the same or new operators. EPMM exploits enable persistent accessThe recently disclosed security flaws in Ivanti Endpoint Manager Mobile (EPMM) have been exploited by bad actors to establish a reverse shell, deliver JSP web shells, conduct reconnaissance, and download malware, including Nezha, cryptocurrency miners, and backdoors for remote access. The two critical vulnerabilities, CVE-2026-1281 and CVE-2026-1340, allow unauthenticated attackers to remotely execute arbitrary code on target servers, granting them full control over mobile device management (MDM) infrastructure without requiring user interaction or credentials. According to Palo Alto Networks Unit 42, the campaign has affected state and local government, healthcare, manufacturing, professional and legal services, and high technology sectors in the U.S., Germany, Australia, and Canada. "Threat actors are accelerating operations, moving from initial reconnaissance to deploying dormant backdoors designed to maintain long-term access even after organizations apply patches," the cybersecurity company said. In a related development, Germany's Federal Office for Information Security (BSI) has reported evidence of exploitation since the summer of 2025 and has urged organizations to audit their systems for indicators of compromise (IoCs) as far back as July 2025. AI passwords lack true randomnessNew research by Irregular has found that passwords generated directly by a large language model (LLM) may appear strong but are fundamentally insecure, as "LLMs are designed to predict tokens – the opposite of securely and uniformly sampling random characters." The artificial intelligence (AI) security company said it detected LLM-generated passwords in the real world as part of code development tasks instead of leaning on traditional secure password generation methods. "People and coding agents should not rely on LLMs to generate passwords," the company said. "LLMs are optimized to produce predictable, plausible outputs, which is incompatible with secure password generation. AI coding agents should be directed to use secure password generation methods instead of relying on LLM-output passwords. Developers using AI coding assistants should review generated code for hardcoded credentials and ensure agents use cryptographically secure methods or established password managers." PDF engine flaws enable account takeoverCybersecurity researchers have discovered more than a dozen vulnerabilities (CVE-2025-70401, CVE-2025-70402, and CVE-2025-66500) in popular PDF platforms from Foxit and Apryse, potentially allowing attackers to exploit them for account takeover, session hijacking, data exfiltration, and arbitrary JavaScript execution. "Rather than isolated bugs, the issues cluster around recurring architectural failures in how PDF platforms handle untrusted input across layers," Novee Security researchers Lidor Ben Shitrit, Elad Meged, and Avishai Fradlis said. "Several vulnerabilities were exploitable with a single request and affected trusted domains commonly embedded inside enterprise applications." The issues have been addressed by both Apryse and Foxit through product updates. Training labs expose cloud backdoorsA "widespread" security issue has been discovered where security vendors inadvertently expose deliberately vulnerable training applications, such as OWASP Juice Shop, DVWA, bWAPP, and Hackazon, to the public internet. This can open organizations to severe security risks when they are executed from a privileged cloud account. "Primarily deployed for internal testing, product demonstrations, and security training, these applications were frequently left accessible in their default or misconfigured states," Pentera Labs said. "These critical flaws not only allowed attackers full control over the compromised compute engine but also provided pathways for lateral movement into sensitive internal systems. Violations of the principle of least privilege and inadequate sandboxing measures further facilitated privilege escalation, endangering critical infrastructure and sensitive organizational data." Further analysis has determined that threat actors are exploiting this blind spot to plant web shells, cryptocurrency miners, and persistence mechanisms on compromised systems. Evasion loader refines C2 stealthThe malware loader known as Oyster (aka Broomstick or CleanUpLoader) has continued to evolve into early 2026, fine-tuning its C2 infrastructure and obfuscation methods, per findings from Sekoia. The malware is distributed mainly through fake websites that distribute installers for legitimate software like Microsoft Teams, with the core payload often deployed as a DLL for persistent execution. "The initial stage leverages excessive legitimate API call hammering and simple anti-debugging traps to thwart static analysis," the company said. "The core payload is delivered in a highly obfuscated manner. The final stage implements a robust C2 communication protocol that features a dual-layer server infrastructure and highly-customized data encoding." Stealer taunts researchers in codeNoodlophile is the name given to an information-stealing malware that has been distributed via fake AI tools promoted on Facebook. Assessed to be the work of a threat actor based in Vietnam, it was first documented by Morphisec in May 2025. Since then, there have been other reports detailing various campaigns, such as UNC6229 and PXA Stealer, orchestrated by Vietnamese cybercriminals. Morphisec's latest analysis of Noodlophile has revealed that the threat actor "padded the malware with millions of repeats of a colorful Vietnamese phrase translating to 'f*** you, Morphisec,'" suggesting that the operators were not thrilled about getting exposed. "Not just to vent frustration over disrupted campaigns, but also to bloat the file and crash AI-based analysis tools that are based on the Python disassemble library – dis.dis(obj)," security researcher Michael Gorelik said. Crypto library RCE risk patchedThe OpenSSL project has patched a stack buffer overflow flaw that can lead to remote code execution attacks under certain conditions. The vulnerability, tracked as CVE-2025-15467, resides in how the library processes Cryptographic Message Syntax data. Threat actors can use CMS packets with maliciously crafted AEAD parameters to crash OpenSSL and run malicious code. CVE-2025-15467 is one of 12 issues that were disclosed by AISLE late last month. Another high-severity vulnerability is CVE-2025-11187, which could trigger a stack-based buffer overflow due to a missing validation. Machine accounts expand delegation riskNew research from Silverfort has cleared a "common assumption" that Kerberos delegation -- which allows a service to request resources or perform actions on behalf of a user -- applies not just to human users, but also to machine accounts as well. In other words, a computer account can be delegated on behalf of highly privileged machine identities such as domain controllers. "That means a service trusted for delegation can act not just on behalf of other users, but also on behalf of machine accounts, the most critical non-human identities (NHIs) in any domain," Silverfort researcher Dor Segal said. "The risk is obvious. If an adversary can leverage delegation, it can act on behalf of sensitive machine accounts, which in many environments hold privileges equivalent to Domain Administrator." To counter the risk, it's advised to run "Set-ADAccountControl -Identity “HOST01$” -AccountNotDelegated $true" for each sensitive machine account. Security news rarely breaks in isolation. One incident leads to another, new research builds on older findings, and attacker playbooks keep adjusting along the way. The result is a constant stream of signals that are easy to miss without a structured view. This roundup pulls those signals together into a single, readable snapshot. Go through the full list to get quick clarity on the developments shaping defender priorities and risk conversations right now.
thehackernews.comFeb 19, 2026extracted
AI Found Twelve New Vulnerabilities in OpenSSL
AI Found Twelve New Vulnerabilities in OpenSSL The title of the post is”What AI Security Research Looks Like When It Works,” and I agree: In the latest OpenSSL security release> on January 27, 2026, twelve new zero-day vulnerabilities (meaning unknown to the maintainers at time of disclosure) were announced. Our AI system is responsible for the original discovery of all twelve, each found and responsibly disclosed to the OpenSSL team during the fall and winter of 2025. Of those, 10 were assigned CVE-2025 identifiers and 2 received CVE-2026 identifiers. Adding the 10 to the three we already found in the Fall 2025 release, AISLE is credited for surfacing 13 of 14 OpenSSL CVEs assigned in 2025, and 15 total across both releases. This is a historically unusual concentration for any single research team, let alone an AI-driven one. These weren’t trivial findings either. They included CVE-2025-15467, a stack buffer overflow in CMS message parsing that’s potentially remotely exploitable without valid key material, and exploits for which have been quickly developed online. OpenSSL rated it HIGH severity; NIST‘s CVSS v3 score is 9.8 out of 10 (CRITICAL, an extremely rare severity rating for such projects). Three of the bugs had been present since 1998-2000, for over a quarter century having been missed by intense machine and human effort alike. One predated OpenSSL itself, inherited from Eric Young’s original SSLeay implementation in the 1990s. All of this in a codebase that has been fuzzed for millions of CPU-hours and audited extensively for over two decades by teams including Google’s. In five of the twelve cases, our AI system directly proposed the patches that were accepted into the official release. AI vulnerability finding is changing cybersecurity, faster than expected. This capability will be used by both offense and defense. More.
schneier.comFeb 18, 2026extracted
Autonomous System Uncovers Long-Standing OpenSSL Flaws
A coordinated security update released earlier this month fixed 12 previously unknown vulnerabilities in OpenSSL, the open-source cryptographic library that underpins a large share of the world’s secure communications. The issues were uncovered by AISLE and disclosed through a coordinated process with the OpenSSL project. OpenSSL is one of the most scrutinized codebases in existence. Even a single accepted vulnerability is considered rare due to decades of review by maintainers and external researchers. Several of the newly addressed flaws had existed in the code for years, with some dating back to 1998, highlighting both the maturity of the library and the difficulty of identifying subtle defects. Multiple High and Low Severity Flaws In a new advisory published on Tuesday, AISLE revealed it began autonomously analyzing OpenSSL in August 2025, building on earlier disclosures made later that year. The January 2026 release consolidated all remaining findings into a single coordinated update. The vulnerabilities spanned more than eight subsystems, ranging from cryptographic message syntax to newer components such as QUIC and post-quantum signature handling. The release included issues of varying severity, including a high-severity stack buffer overflow in CMS AuthEnvelopedData parsing that could enable remote code execution (RCE) under specific conditions. A moderate-severity flaw affecting PKCS#12 parameter validation was also resolved. The remaining issues were classified as low severity and largely involved crashes, memory corruption, encryption edge cases or resource exhaustion. AISLE also recommended remediation steps, with fixes for five of the 12 vulnerabilities incorporated directly into OpenSSL’s code. Collaboration and Broader Impact According to Tomáš Mráz, chief technical officer (CTO) of the OpenSSL Foundation, independent research remains central to the project’s security. “This release is fixing 12 security issues, all disclosed to us by AISLE,” he said. “We appreciate the high quality of the reports and their constructive collaboration with us throughout the remediation.” Beyond the published CVEs, AISLE identified six additional issues that were resolved before appearing in any OpenSSL release. These fixes were merged during development, preventing vulnerable code from reaching users. AISLE explained how the findings highlight the limits of manual review and traditional static analysis in large, long-lived codebases. Autonomous analysis can continuously examine edge cases and complex logic paths at scale, while still relying on maintainers’ expertise to validate results and implement robust fixes. “Keeping widely deployed cryptography secure requires tight coordination between maintainers and researchers,” said Matt Caswell, executive director of the OpenSSL Foundation. “We appreciate AISLE’s responsible disclosures and the quality of their engagement across these issues.”
infosecurity-magazine.comJan 28, 2026extracted
OpenSSL: 12 bug di sicurezza rilevati tra i quali una vulnerabilità critica
Betti RHC, la prima graphic novel al mondo dedicata alla cybersecurity awareness, ha finalmente il suo sito ufficiale. Uno spazio tutto suo dove scoprire il progetto, sfogliare le copertine degli episodi e immergersi nel mondo di Betti: la giovane laureanda in informatica che, dopo la morte misteriosa del padre, si trasforma nell'hacker più potente del mondo. Una storia avvincente che, episodio dopo episodio, affronta una minaccia digitale diversa — dal phishing al ransomware, fino al cyberbullismo — e insegna a riconoscerla e a difendersi, senza che sembri mai una lezione. Sul sito trovate tutto ciò che rende Betti un progetto diverso dal solito: la sua filosofia, le anteprime delle tavole e il racconto di come nasce ogni volume. Perché dietro Betti RHC c'è solo lavoro umano: ogni tavola è disegnata interamente a mano dagli artisti del Gruppo Arte di Red Hot Cyber, senza alcun uso di intelligenza artificiale. E a garantire che ogni storia sia realistica e tecnicamente corretta c'è la supervisione degli hacker etici del gruppo HackerHood, che mantengono il racconto fedele al mondo reale della sicurezza informatica. C'è spazio anche per le aziende, che possono usare Betti come strumento di awareness diverso dai soliti corsi: acquistare i volumi, personalizzarli con il proprio brand o sponsorizzare nuovi episodi. E come primo regalo, l'episodio "Byte the Silence", dedicato al cyberbullismo, è scaricabile gratuitamente per uso personale. Perché la miglior difesa, in fondo, è una bella storia. 👉 Scopri tutto su https://betti.redhotcyber.com/
redhotcyber.comJan 28, 2026extracted
High-Severity Remote Code Execution Vulnerability Patched in OpenSSL
OpenSSL updates released on Tuesday patch a dozen vulnerabilities, including a high-severity remote code execution flaw. All 12 vulnerabilities patched in the open source SSL/TLS toolkit were discovered by cybersecurity firm Aisle, which used an autonomous analyzer to identify the security holes. The high-severity issue is tracked as CVE-2025-15467 and it has been described as a stack buffer overflow that could lead to a crash (DoS condition) or remote code execution in certain conditions. OpenSSL maintainers explained in their advisory: When parsing CMS AuthEnvelopedData structures that use AEAD ciphers such as AES-GCM, the IV (Initialization Vector) encoded in the ASN.1 parameters is copied into a fixed-size stack buffer without verifying that its length fits the destination. An attacker can supply a crafted CMS message with an oversized IV, causing a stack-based out-of-bounds write before any authentication or tag verification occurs. Applications and services that parse untrusted CMS or PKCS#7 content using AEAD ciphers (e.g., S/MIME AuthEnvelopedData with AES-GCM) are vulnerable. Because the overflow occurs prior to authentication, no valid key material is required to trigger it. While exploitability to remote code execution depends on platform and toolchain mitigations, the stack-based write primitive represents a severe risk. The latest OpenSSL releases also address CVE-2025-11187, a moderate-severity issue whose exploitation could also lead to a DoS condition or even remote code execution. The remaining flaws have been classified as low severity. A majority of them can be exploited to cause a DoS condition, and a couple are related to authentication and information exposure. Aisle pointed out that in addition to the 12 vulnerabilitites that have been assigned a CVE, it identified six issues that have been addressed prior to the affected code being included in a release. Related: Microsoft Patches Office Zero-Day Likely Exploited in Targeted Attacks Related: OpenSSL Vulnerabilities Allow Private Key Recovery, Code Execution, DoS Attacks Related: High-Severity OpenSSL Vulnerability Found by Apple Allows MitM Attacks
securityweek.comJan 28, 2026extracted
USN-7980-2: OpenSSL vulnerabilities
Packages openssl - Secure Socket Layer (SSL) cryptographic library and tools openssl1.0 - Secure Socket Layer (SSL) cryptographic library and tools Details USN-7980-1 fixed vulnerabilities in OpenSSL. This update provides the corresponding updates for CVE-2025-68160 for openssl and openssl1.0, CVE-2025-69418 for openssl on Ubuntu 18.04 LTS and Ubuntu 20.04 LTS, CVE-2025-69419 for openssl on Ubuntu 18.04 LTS and Ubuntu 20.04 LTS, CVE-2025-69420 for openssl on Ubuntu 18.04 LTS and Ubuntu 20.04 LTS, CVE-2025-69421 for openssl and openssl1.0, CVE-2026-22795 for openssl on Ubuntu 18.04 LTS and Ubuntu 20.04 LTS, and CVE-2026-22796 for openssl and openssl1.0. Original advisory details: Stanislav Fort, Petr Šimeček, and Hamza discovered that OpenSSL incorrectly validated PBMAC1 parameters when doing PKCS#12 MAC ... USN-7980-1 fixed vulnerabilities in OpenSSL. This update provides the corresponding updates for CVE-2025-68160 for openssl and openssl1.0, CVE-2025-69418 for openssl on Ubuntu 18.04 LTS and Ubuntu 20.04 LTS, CVE-2025-69419 for openssl on Ubuntu 18.04 LTS and Ubuntu 20.04 LTS, CVE-2025-69420 for openssl on Ubuntu 18.04 LTS and Ubuntu 20.04 LTS, CVE-2025-69421 for openssl and openssl1.0, CVE-2026-22795 for openssl on Ubuntu 18.04 LTS and Ubuntu 20.04 LTS, and CVE-2026-22796 for openssl and openssl1.0. Original advisory details: Stanislav Fort, Petr Šimeček, and Hamza discovered that OpenSSL incorrectly validated PBMAC1 parameters when doing PKCS#12 MAC verification. An attacker could possibly use this issue to cause OpenSSL to crash, resulting in a denial of service. This issue only affected Ubuntu 25.10. (CVE-2025-11187) Stanislav Fort discovered that OpenSSL incorrectly parsed CMS AuthEnvelopedData messages. An attacker could possibly use this issue to cause OpenSSL to crash, resulting in a denial of service. (CVE-2025-15467) Stanislav Fort discovered that OpenSSL incorrectly handled memory in the SSL_CIPHER_find() function. An attacker could possibly use this issue to cause OpenSSL to crash, resulting in a denial of service. This issue only affected Ubuntu 25.10. (CVE-2025-15468) Stanislav Fort discovered that the OpenSSL "openssl dgst" command line tool incorrectly truncated data to 16MB. An attacker could posibly use this issue to hide unauthenticated data beyond the 16MB limit. This issue only affected Ubuntu 25.10. (CVE-2025-15469) Tomas Dulka and Stanislav Fort discovered that OpenSSL incorrectly handled memory with TLS 1.3 connections using certificate compression. An attacker could possibly use this issue to consume resources, leading to a denial of service. This issue only affected Ubuntu 25.10. (CVE-2025-66199) Petr Simecek and Stanislav Fort discovered that OpenSSL incorrectly handled memory when writing large data into a BIO chain. An attacker could possibly use this issue to consume resources, leading to a denial of service. (CVE-2025-68160) Stanislav Fort discovered that the OpenSSL OCB API could incorrectly leave final partial blocks unencrypted and unauthenticated. An attacker could possibly use this issue to read or tamper with the affected final bytes. (CVE-2025-69418) Stanislav Fort discovered that OpenSSL incorrectly handled the PKCS12_get_friendlyname() utf-8 conversion. An attacker could possibly use this issue to cause OpenSSL to crash, resulting in a denial of service. (CVE-2025-69419) Luigino Camastra discovered that OpenSSL incorrectly handled ASN1_TYPE validation in the TS_RESP_verify_response() function. An attacker could possibly use this issue to cause OpenSSL to crash, resulting in a denial of service. (CVE-2025-69420) Luigino Camastra discovered that OpenSSL incorrectly handled memory in the PKCS12_item_decrypt_d2i_ex function. An attacker could possibly use this issue to cause OpenSSL to crash, resulting in a denial of service. (CVE-2025-69421) Luigino Camastra discovered that OpenSSL incorrectly handled ASN1_TYPE validation in PKCS#12 parsing. An attacker could possibly use this issue to cause OpenSSL to crash, resulting in a denial of service. (CVE-2026-22795) Luigino Camastra discovered that OpenSSL incorrectly handled ASN1_TYPE validation in the PKCS7_digest_from_attributes() function. An attacker could possibly use this issue to cause OpenSSL to crash, resulting in a denial of service. (CVE-2026-22796) The problem can be corrected by updating your system to the following package versions: Reduce your security exposure Ubuntu Pro provides ten-year security coverage to 25,000+ packages in Main and Universe repositories, and it is free for up to five machines.
ubuntu.comJan 27, 2026extracted
USN-7980-1: OpenSSL vulnerabilities
Details Stanislav Fort, Petr Šimeček, and Hamza discovered that OpenSSL incorrectly validated PBMAC1 parameters when doing PKCS#12 MAC verification. An attacker could possibly use this issue to cause OpenSSL to crash, resulting in a denial of service. This issue only affected Ubuntu 25.10. (CVE-2025-11187) Stanislav Fort discovered that OpenSSL incorrectly parsed CMS AuthEnvelopedData messages. An attacker could possibly use this issue to cause OpenSSL to crash, resulting in a denial of service. (CVE-2025-15467) Stanislav Fort discovered that OpenSSL incorrectly handled memory in the SSL_CIPHER_find() function. An attacker could possibly use this issue to cause OpenSSL to crash, resulting in a denial of service. This issue only affected Ubuntu 25.10. (CVE-2025-15468) Stanislav Fort discovered that the OpenSSL... Stanislav Fort, Petr Šimeček, and Hamza discovered that OpenSSL incorrectly validated PBMAC1 parameters when doing PKCS#12 MAC verification. An attacker could possibly use this issue to cause OpenSSL to crash, resulting in a denial of service. This issue only affected Ubuntu 25.10. (CVE-2025-11187) Stanislav Fort discovered that OpenSSL incorrectly parsed CMS AuthEnvelopedData messages. An attacker could possibly use this issue to cause OpenSSL to crash, resulting in a denial of service. (CVE-2025-15467) Stanislav Fort discovered that OpenSSL incorrectly handled memory in the SSL_CIPHER_find() function. An attacker could possibly use this issue to cause OpenSSL to crash, resulting in a denial of service. This issue only affected Ubuntu 25.10. (CVE-2025-15468) Stanislav Fort discovered that the OpenSSL "openssl dgst" command line tool incorrectly truncated data to 16MB. An attacker could posibly use this issue to hide unauthenticated data beyond the 16MB limit. This issue only affected Ubuntu 25.10. (CVE-2025-15469) Tomas Dulka and Stanislav Fort discovered that OpenSSL incorrectly handled memory with TLS 1.3 connections using certificate compression. An attacker could possibly use this issue to consume resources, leading to a denial of service. This issue only affected Ubuntu 25.10. (CVE-2025-66199) Petr Simecek and Stanislav Fort discovered that OpenSSL incorrectly handled memory when writing large data into a BIO chain. An attacker could possibly use this issue to consume resources, leading to a denial of service. (CVE-2025-68160) Stanislav Fort discovered that the OpenSSL OCB API could incorrectly leave final partial blocks unencrypted and unauthenticated. An attacker could possibly use this issue to read or tamper with the affected final bytes. (CVE-2025-69418) Stanislav Fort discovered that OpenSSL incorrectly handled the PKCS12_get_friendlyname() utf-8 conversion. An attacker could possibly use this issue to cause OpenSSL to crash, resulting in a denial of service. (CVE-2025-69419) Luigino Camastra discovered that OpenSSL incorrectly handled ASN1_TYPE validation in the TS_RESP_verify_response() function. An attacker could possibly use this issue to cause OpenSSL to crash, resulting in a denial of service. (CVE-2025-69420) Luigino Camastra discovered that OpenSSL incorrectly handled memory in the PKCS12_item_decrypt_d2i_ex function. An attacker could possibly use this issue to cause OpenSSL to crash, resulting in a denial of service. (CVE-2025-69421) Luigino Camastra discovered that OpenSSL incorrectly handled ASN1_TYPE validation in PKCS#12 parsing. An attacker could possibly use this issue to cause OpenSSL to crash, resulting in a denial of service. (CVE-2026-22795) Luigino Camastra discovered that OpenSSL incorrectly handled ASN1_TYPE validation in the PKCS7_digest_from_attributes() function. An attacker could possibly use this issue to cause OpenSSL to crash, resulting in a denial of service. (CVE-2026-22796) The problem can be corrected by updating your system to the following package versions: Reduce your security exposure Ubuntu Pro provides ten-year security coverage to 25,000+ packages in Main and Universe repositories, and it is free for up to five machines.
ubuntu.comJan 27, 2026extracted
USN-7894-2: EDK II regression
Details USN-7894-1 fixed vulnerabilities in EDK II. The update introduced a regression in the UEFI network boot. This update reverts the corresponding fixes for CVE-2023-45236 and CVE-2023-45237 pending further investigation. We apologize for the inconvenience. Original advisory details: It was discovered that EDK II was susceptible to a predictable TCP Initial Sequence Number. An attacker could possibly use this issue to gain unauthorized access. This issue only affected Ubuntu 22.04 LTS, and Ubuntu 24.04 LTS. (CVE-2023-45236, CVE-2023-45237) It was discovered that EDK II incorrectly handled S3 sleep. An attacker could possibly use this issue to cause a denial of service. This issue only affected Ubuntu 22.04 LTS, and Ubuntu 24.04 LTS. ( USN-7894-1 fixed vulnerabilities in EDK II. The update introduced a regression in the UEFI network boot. This update reverts the corresponding fixes for CVE-2023-45236 and CVE-2023-45237 pending further investigation. We apologize for the inconvenience. Original advisory details: It was discovered that EDK II was susceptible to a predictable TCP Initial Sequence Number. An attacker could possibly use this issue to gain unauthorized access. This issue only affected Ubuntu 22.04 LTS, and Ubuntu 24.04 LTS. (CVE-2023-45236, CVE-2023-45237) It was discovered that EDK II incorrectly handled S3 sleep. An attacker could possibly use this issue to cause a denial of service. This issue only affected Ubuntu 22.04 LTS, and Ubuntu 24.04 LTS. (CVE-2024-1298) It was discovered that the EDK II PE/COFF loader incorrectly handled certain memory operations. An attacker could possibly use this issue to cause a denial of service, obtain sensitive information, or execute arbitrary code. This issue only affected Ubuntu 22.04 LTS, and Ubuntu 24.04 LTS. (CVE-2024-38796) It was discovered that the EDK II PE image hashing function incorrectly handled certain memory operations. An attacker could possibly use this issue to cause a denial of service, or execute arbitrary code. (CVE-2024-38797) It was discovered that the EDK II BIOS incorrectly handled certain memory operations. An attacker could possibly use this issue to cause a denial of service. (CVE-2024-38805, CVE-2025-2295) It was discovered that EDK II incorrectly handled the enabling of MCE. An attacker could possibly use this issue to cause a denial of service, or execute arbitrary code. (CVE-2025-3770) It was discovered that the OpenSSL library embedded in EDK II contained multiple vulnerabilties. An attacker could possibly use these issues to cause a denial of service, obtain sensitive information, or execute arbitrary code. (CVE-2021-3712, CVE-2022-0778, CVE-2022-4304, CVE-2022-4450, CVE-2023-0215, CVE-2023-0286, CVE-2023-0464, CVE-2023-0465, CVE-2023-0466, CVE-2023-2650, CVE-2023-3446, CVE-2023-3817, CVE-2023-5678, CVE-2023-6237, CVE-2024-0727, CVE-2024-13176, CVE-2024-2511, CVE-2024-41996, CVE-2024-4741, CVE-2024-5535, CVE-2024-6119, CVE-2024-9143, CVE-2025-9232) The problem can be corrected by updating your system to the following package versions: Reduce your security exposure Ubuntu Pro provides ten-year security coverage to 25,000+ packages in Main and Universe repositories, and it is free for up to five machines.
ubuntu.comNov 28, 2025extracted
Loading 14 more…