On February 4, 2026, KRVTZ-NET IDS detected network reconnaissance activity targeting Fortigate VPN devices, specifically scanning the /remote/logincheck endpoint associated with CVE-2023-27997. This vulnerability could allow unauthorized access or remote code execution. No active exploitation or payload delivery was observed, and no patches are currently available for this specific alert. The activity is low severity and likely represents early-stage reconnaissance. European organizations using Fortigate VPNs, especially in critical infrastructure and government sectors, should be aware of this scanning activity.
CVE-2026-24667 is a medium-severity vulnerability in the Open eClass platform versions prior to 4.2, where active user sessions are not invalidated after a password change. This insufficient session expiration (CWE-613) allows attackers who have access to existing session tokens to maintain unauthorized access even after the user updates their password. The vulnerability does not require user interaction but does require low privileges and has a network attack vector with high attack complexity. It impacts confidentiality, integrity, and availability to a limited extent. The issue has been patched in version 4.2, and no known exploits are currently reported in the wild. European organizations using Open eClass should prioritize upgrading to the patched version to mitigate risks associated with session hijacking post-password change.
The KRVTZ-NET IDS alerts from February 3, 2026, report automated reconnaissance activity detected by intrusion detection systems, involving IP addresses linked to Censys, a known internet scanning service. This activity is categorized as reconnaissance in the cyber kill chain and involves scanning HTTP User-Agent strings to gather information about potential targets. No specific vulnerabilities, exploits, or malware are associated with these alerts, and no active exploitation is reported. The severity is low, reflecting the preliminary nature of reconnaissance without direct impact on confidentiality, integrity, or availability. European organizations should treat this as an early warning and maintain vigilance, as reconnaissance can precede targeted attacks. Mitigation involves network monitoring, tuning IDS/IPS to detect scanning patterns, network segmentation, and maintaining asset inventories. No patches or immediate remediation are required. The threat is low severity but warrants continued observation to prevent escalation.
Improper Verification of Cryptographic Signature vulnerability in liuyueyi quick-media (plugins/svg-plugin/batik-codec-fix/src/main/java/org/apache/batik/ext/awt/image/codec/util modules). This vulnerability is associated with program files SeekableOutputStream.Java.
This issue affects quick-media: before v1.0.
Improper Control of Generation of Code ('Code Injection') vulnerability in liuyueyi quick-media (plugins/svg-plugin/batik-codec-fix/src/main/java/org/apache/batik/ext/awt/image/codec/png modules). This vulnerability is associated with program files PNGImageEncoder.Java.
This issue affects quick-media: before v1.0.
Improper Restriction of Operations within the Bounds of a Memory Buffer vulnerability in CardboardPowered cardboard (src/main/java/org/cardboardpowered/impl/world modules). This vulnerability is associated with program files WorldImpl.Java.
This issue affects cardboard: before 1.21.4.
Integer Overflow or Wraparound vulnerability in MuntashirAkon AppManager (app/src/main/java/org/apache/commons/compress/archivers/tar modules). This vulnerability is associated with program files TarUtils.Java.
This issue affects AppManager: before 4.0.4.
Red Hat OpenShift AI 3.2 has been released with updates addressing security issues identified by CVE-2025-62593 and CVE-2025-66418. The advisory notes the availability of updated images and provides guidance for upgrading clusters to apply the errata update. No specific fixes or technical details about the vulnerabilities are disclosed in the advisory. The vulnerabilities are associated with CWE-94 (Improper Control of Generation of Code), CWE-770 (Allocation of Resources Without Limits or Throttling), and CWE-352 (Cross-Site Request Forgery).
A security update for python-weasyprint addresses a server-side request forgery (SSRF) vulnerability identified as CVE-2025-68616. The issue was present in the default fetcher component of python-weasyprint. This vulnerability could allow an attacker to induce the server to make unintended requests. The update fixes this SSRF vulnerability, mitigating the associated risk.
KRVTZ IDS alerts from January 14, 2026, report automated network reconnaissance and brute force attempts targeting Postfix mail servers. Multiple IP addresses were identified attempting SASL authentication brute forcing, with these attempts detected and blocked. One IP was also flagged for spam activity blocked via DNSBL. These activities represent the reconnaissance phase of attacks, aiming to discover valid credentials or vulnerable configurations. No specific vulnerabilities or exploits are associated, and no patches are available or needed. The threat is low severity due to the lack of successful compromises and absence of denial-of-service indicators. However, persistent brute forcing could lead to credential compromise if defenses are weak. The threat primarily affects European organizations running Postfix servers, with countries like Germany, France, and the UK most likely impacted. Effective monitoring, strong authentication policies, and dynamic IP blocking are critical to mitigating this threat.
Hackers exploited a multisignature (multisig) wallet vulnerability in the Unleash Protocol, resulting in the theft of approximately $3.9 million. The attack involved hijacking control over the multisig wallet, which is designed to require multiple approvals for transactions, thereby bypassing its intended security. This incident highlights risks associated with multisig wallet management and governance in decentralized finance (DeFi) platforms. Although no specific CVEs or patches are currently available, the breach demonstrates a high-severity threat due to the large financial loss and potential for similar attacks on other DeFi protocols. European organizations involved in blockchain, cryptocurrency, or DeFi services could face significant financial and reputational damage if targeted. Mitigation requires robust multisig wallet security practices, including strict key management, enhanced access controls, and continuous monitoring for suspicious activity. Countries with active blockchain ecosystems and financial hubs, such as Germany, the Netherlands, Switzerland, and the UK, are most likely to be affected. Given the attack's impact on confidentiality, integrity, and availability of funds, ease of exploitation through governance compromise, and lack of user interaction, the suggested severity is high. Defenders should prioritize securing multisig wallets and governance processes to prevent similar hijacks.
Disney has agreed to pay $10 million to settle a lawsuit alleging violations of children's data privacy on YouTube. The case centers on claims that Disney improperly collected and used personal data from children without adequate consent or safeguards, violating privacy regulations. While this is a significant legal and financial consequence for Disney, it does not represent a direct technical vulnerability or exploit. The settlement highlights the increasing regulatory scrutiny on companies handling children's data, especially in digital and online platforms. European organizations should note the importance of compliance with data protection laws such as GDPR and the ePrivacy Directive, which impose strict requirements on processing children's personal data. This case underscores the risks of non-compliance, including costly legal actions and reputational damage. No active exploits or technical attack vectors are associated with this event. Organizations should review their data collection practices, especially for minors, and ensure transparency, parental consent, and data minimization. Countries with strong data protection enforcement and significant digital media markets, such as Germany, France, and the UK, are particularly relevant in this context. Overall, this incident is a legal and compliance issue rather than a cybersecurity threat or vulnerability requiring technical mitigation.
The U. S. Treasury has lifted sanctions on three individuals linked to Intellexa and Predator spyware, a development that may influence the regulatory and threat landscape surrounding these spyware tools. Intellexa and Predator spyware have been associated with surveillance and cyber espionage activities, often targeting activists, journalists, and political opponents. Although no new technical vulnerabilities or exploits are reported in this announcement, the removal of sanctions could affect the availability and distribution of these spyware tools. European organizations should be aware of potential shifts in spyware deployment or vendor operations resulting from this policy change. The threat does not involve direct exploitation or vulnerabilities but relates to geopolitical and regulatory factors impacting spyware proliferation. Mitigation should focus on enhanced detection capabilities for spyware behaviors and monitoring of communications for signs of Predator or Intellexa spyware activity. Countries with significant use of surveillance technology or high-profile political targets, such as France, Germany, Italy, Spain, and the UK, may be more affected. Given the indirect nature of the threat and absence of new exploits, the suggested severity is medium.
A former Coinbase support agent was arrested for assisting hackers in compromising user accounts. This insider threat highlights risks associated with privileged access abuse within cryptocurrency platforms. Although no specific technical exploit details or affected software versions are provided, the incident underscores the potential for social engineering and insider collusion to facilitate unauthorized access. European organizations involved in cryptocurrency trading or custodial services could face similar insider risks. Mitigation requires stringent internal controls, enhanced monitoring of privileged users, and robust verification processes for support interactions. Countries with significant cryptocurrency adoption and financial sectors, such as Germany, the UK, and the Netherlands, are most likely to be impacted. The threat severity is assessed as high due to the potential for significant financial loss and reputational damage, ease of exploitation via insider access, and the broad impact on user trust. Defenders should prioritize insider threat programs and continuous behavioral analytics to detect anomalous support agent activities.
The OWASP Agentic AI Top 10 highlights the most critical security risks associated with agentic AI systems, reflecting real-world attack scenarios. These attacks exploit vulnerabilities in AI agents that operate autonomously or semi-autonomously, potentially leading to unauthorized actions, data breaches, or manipulation of AI behavior. Although no specific CVEs or exploits are currently documented in the wild, the high severity rating underscores the significant risk posed by these emerging threats. European organizations leveraging agentic AI technologies must be vigilant, as these systems can impact confidentiality, integrity, and availability of critical services. Mitigations require tailored security controls focusing on AI model governance, input validation, and monitoring of AI decision-making processes. Countries with advanced AI adoption and critical infrastructure integration, such as Germany, France, and the UK, are more likely to be affected. Given the complexity and novelty of agentic AI threats, the suggested severity is high, reflecting the potential for substantial operational and reputational damage if exploited. Defenders should prioritize understanding these AI-specific risks and implement robust AI security frameworks to mitigate emerging attack vectors.
A MongoDB exploit targeting Ubisoft's Rainbow Six Siege players led to the temporary shutdown of the game. The exploit leveraged vulnerabilities in MongoDB instances related to player data or game infrastructure, causing significant disruption. Although no known exploits in the wild have been confirmed, the incident was severe enough to prompt Ubisoft to halt game operations. The attack highlights risks associated with improperly secured MongoDB deployments. European organizations connected to Ubisoft or using similar MongoDB configurations may face risks of data exposure or service disruption. Mitigation requires securing MongoDB instances with authentication, network restrictions, and regular patching. Countries with strong gaming markets and Ubisoft presence, such as France and Germany, are most likely affected. The threat is assessed as high severity due to potential data compromise and service availability impact without requiring user interaction. Defenders should prioritize immediate MongoDB security audits and incident response readiness.
In mid-2025, a malicious driver file was discovered on Asian computer systems, signed with a compromised digital certificate. This driver injects a backdoor Trojan and protects malicious files, processes, and registry keys. The final payload is a new variant of the ToneShell backdoor, associated with the HoneyMyte APT group. The attacks, which began in February 2025, primarily target government organizations in Southeast and East Asia, especially Myanmar and Thailand. The malware uses various techniques to evade detection, including API obfuscation, process protection, and registry key protection. The ToneShell backdoor communicates with command-and-control servers using fake TLS headers and supports remote operations such as file transfer and shell access.
A hacker has claimed to leak a database belonging to WIRED containing approximately 2.3 million records. The breach was reported via a Reddit post in the InfoSecNews subreddit and covered by a trusted cybersecurity news source, BleepingComputer. Although the exact nature of the leaked data and the method of compromise are not detailed, the incident is classified as a high-severity data breach. There are no known exploits in the wild related to this breach, and technical details remain sparse. The leak potentially exposes sensitive information of users or subscribers associated with WIRED. European organizations may be indirectly impacted if their employees or partners' data is included or if they rely on WIRED’s services. Mitigation focuses on monitoring for data misuse, enhancing incident response, and reviewing third-party data sharing agreements. Countries with significant media consumption and digital engagement, such as the UK, Germany, and France, are more likely to be affected. Given the scale and sensitivity of the data leak, the suggested severity is high due to the potential confidentiality impact and the broad scope of affected individuals without requiring authentication or user interaction.
The pro-Russian hacktivist group Noname057 has claimed responsibility for a cyberattack targeting La Poste services in France. The attack was reported via Reddit and linked to a news article but lacks detailed technical information or confirmed impact assessments. No specific vulnerabilities, exploited methods, or affected system versions have been disclosed, and there are no known exploits in the wild associated with this campaign. The severity is assessed as medium based on the nature of the target and the potential disruption to postal services. European organizations, especially those in France, could face operational disruptions and data confidentiality risks if the attack is substantiated. Mitigation should focus on enhancing monitoring of La Poste’s digital infrastructure, incident response readiness, and communication security. Countries with significant reliance on La Poste or similar postal services and with geopolitical tensions involving Russia are more likely to be affected. Given the limited technical details and lack of confirmed exploitation, the suggested severity remains medium. Defenders should prioritize vigilance and verification of La Poste’s security posture while preparing for potential escalation or follow-up attacks.