Search: ic-controls.com
1,438 threats
Most recently published first
| Severity | CVSS | Signals | Threat | Source | Published | Score and star |
|---|---|---|---|---|---|---|
| –Not rated | – | AlienVault OTX General Analysis of 4 million dynamic malware reports reveals that 45.32% of malware samples with command-and-control activity establish direct-to-IP (D2IP) connections, bypassing DNS entirely and evading DNS-based security defenses. D2IP traffic accounts for 23.17% of all C2 connection attempts. This behavior is observed across diverse threats including Phorpiex ransomware droppers using hard-coded IP addresses, persistent data exfiltration campaigns employing obfuscated HTTP GET requests, SectopRAT targeting educational institutions with in-browser proxy capabilities, and IoT botnets like Mozi and Boatnet propagating through P2P networks. The research introduces zero trust IP (ZT-IP), a network-level enforcement approach that verifies whether outbound connection destinations were previously sanctioned by DNS responses, effectively blocking malicious D2IP communications that traditional DNS-based security controls cannot detect. | AlienVault OTX General | |||
| Medium | 5.3 | EPSS 0.4% | CVE-2026-18722diaowen DWSurvey · Authorization Bypass Medium5.3EPSS 0.4%CVE Database V5CVE-2026-18722 CVE-2026-18722 is an authorization bypass vulnerability in diaowen DWSurvey versions up to 6.14.0. It affects the devSurvey function in the DwDeisgnSurveyController component, allowing remote attackers to bypass authorization controls. The vulnerability has a medium severity with a CVSS score of 5.3. Exploit code has been publicly disclosed, but there are no known exploits in the wild. The vendor has not responded to the disclosure, and no official patch or remediation is currently available. EPSS 0.4%Vulnerability | CVE Database V5 | ||
| Medium | 5.3 | EPSS 0.4% | CVE-2026-18631jeequan jeepay · Authorization Bypass Medium5.3EPSS 0.4%CVE Database V5CVE-2026-18631 CVE-2026-18631 is an authorization bypass vulnerability in jeequan jeepay affecting versions 3.2.0 through 3.2.9. It involves the WebSecurityConfig function in the SysLogController component, allowing remote attackers to bypass authorization controls. The vulnerability has a medium severity score of 5.3. No official patch or vendor response has been documented, and public exploit code is available. EPSS 0.4%Vulnerability | CVE Database V5 | ||
| Medium | 6.9 | EPSS 0.7% | CVE-2026-18610NewType WebEIP · Improper Authentication Medium6.9EPSS 0.7%CVE Database V5CVE-2026-18610 CVE-2026-18610 is an improper authentication vulnerability in NewType WebEIP version 3.0 affecting the /EIP_Com_FileList.aspx file. The flaw allows remote attackers to bypass authentication controls. Public exploit code is available, but no vendor response or patch has been provided. The vulnerability has a medium severity rating with a CVSS score of 6.9. EPSS 0.7%Vulnerability | CVE Database V5 | ||
| Critical | 9.1 | EPSS 0.3% | Critical9.1EPSS 0.3%CVE Database V5CVE-2026-9487 XML::Sig versions before 0.71 for Perl contain a critical vulnerability that allows signature wrapping via duplicate ID values. The _get_signed_xml() function resolves SignedInfo Reference/@URI by selecting the first node with a matching ID, but does not detect if multiple elements share that ID. This can cause a document with duplicate IDs to verify successfully while an attacker controls the second element, potentially compromising SAML2 assertions. | CVE Database V5 | ||
| Medium | 4.8 | EPSS 0.1% | Medium4.8EPSS 0.1%CVE Database V5CVE-2026-34490 Cleartext storage of sensitive information vulnerability in Johnson Controls XAAP Application on Android allows an attacker on a jailbroken or otherwise compromised device to Retrieve Sensitive Data. This issue affects XAAP Application: before 1.53. | CVE Database V5 | ||
| High | 7.5 | EPSS 0.7% | CVE-2026-17347pgAdmin 4 · OS Command Injection High7.5EPSS 0.7%CVE Database V5CVE-2026-17347 The MASTER_PASSWORD_HOOK setting, introduced in pgAdmin 4 7.2, lets an administrator configure an external command that returns a per-user encryption key, with %u in the configured string replaced by the current user's name. The previous implementation substituted the username directly into the command string and executed the result with subprocess.Popen(..., shell=True). Because the username can originate from an external authentication source (OAuth/OIDC claims, Kerberos, webserver auth) rather than a value pgAdmin fully controls, a username containing shell metacharacters (';', '$()', backticks, pipes, '&&', newlines) allowed an authenticated user to execute arbitrary commands as the pgAdmin service account in any deployment where the configured hook string uses %u. Fix tokenises the trusted, administrator-configured hook string into an argument vector first (using shlex in POSIX-quoting mode, with backslash-escaping disabled so Windows-style paths are not mis-parsed), substitutes the untrusted username into the individual argv elements, and executes with shell=False. The username is therefore always confined to a single argv element; any shell metacharacters it contains are inert. Administrators whose MASTER_PASSWORD_HOOK previously relied on shell features (pipes, redirection, environment-variable expansion, globbing) within the hook string itself must move that logic into the invoked script, since it is no longer interpreted by a shell. This issue affects pgAdmin 4: from 7.2 before 9.17. | CVE Database V5 | ||
| Low | 2.1 | EPSS 0.2% | CVE-2026-65636ufirstgroup ymlr · CRLF Injection Low2.1EPSS 0.2%CVE Database V5CVE-2026-65636 Improper Neutralization of CRLF Sequences vulnerability in ufirstgroup ymlr (Elixir.Ymlr module) allows attackers to inject arbitrary content into generated YAML documents through document comments. Ymlr.document!/2 interpolates each caller-supplied comment string into the output behind a single # prefix without validating it or escaping line breaks. Because a YAML comment is terminated by a line break, the first carriage return or line feed in the comment string ends the comment context and everything after it is emitted at column 0 of the document body. An attacker who controls text that the host application passes as a comment can forge top-level mapping keys, override values the application itself set, and emit --- or ... markers that split the output into additional documents. Downstream consumers of the generated YAML, such as configuration loaders, deployment manifests, CI pipelines and data importers, parse the injected content as legitimate data. The same clause backs Ymlr.document/2, Ymlr.documents!/2 and Ymlr.documents/2, so every document encoding entry point is affected. This vulnerability is associated with program files lib/ymlr.ex and program routines 'Elixir.Ymlr':document!/2, 'Elixir.Ymlr':documents!/2. This issue affects ymlr from 0.0.1 before 5.1.6. | CVE Database V5 | ||
| Medium | 5.3 | EPSS 0.2% | CVE-2026-10031drakkan SFTPGo · Incorrect Authorization Medium5.3EPSS 0.2%CVE Database V5CVE-2026-10031 SFTPGo prior to 2.7.4 contains a permission bypass vulnerability that allows authenticated users to circumvent per-directory access controls by creating symbolic links in a permitted directory that point to files in directories where download, upload, or overwrite permissions are denied. Attackers can exploit the create_symlinks permission combined with read and write access in one directory to read or modify files in restricted directories, as operations are authorized against the link's directory permissions rather than the dereferenced target's directory permissions. EPSS 0.2%Vulnerability | CVE Database V5 | ||
| Critical | 9.8 | EPSS 1.0% | Critical9.8EPSS 1.0%GCVE DatabaseCVE-2026-15969 Overview Six vulnerabilities have been discovered within the SGLang project, including remote code execution (RCE), server-side request forgery (SSRF), local file read, credential leakage, and model weight exfiltration on a target server. Exploitation does not require authentication in most cases, and some vulnerabilities require only network access with no API keys or user credentials. At the time of publication, no patches are available from the project maintainers, and coordination attempts have been unsuccessful. Description SGLang is an open-source framework for serving large language models (LLMs) and multimodal AI models, supporting models such as Qwen, DeepSeek, Mistral, and Skywork, and is compatible with OpenAI APIs. Six vulnerabilities have been discovered within the tool and are tracked as follows: CVE-2026-15969 SGLang contains unauthenticated RCE in /load_lora_adapter_from_tensors by bypass of SafeUnpickler’s incomplete denylist, allowing arbitrary command execution through crafted base64-encoded pickle payloads. CVE-2026-15971 SGLang contains an RCE vulnerability when the optional dumper subsystem is enabled, which allows for a sandbox escape when DUMPER_SERVER_PORT is set, enabling code execution on inference requests. CVE-2026-15974 SGLang contains an SSRF and local file read in the multimodal generation endpoint /v1/chat/completions because image_url input is unsanitized, allowing access to internal metadata, secrets, and services. CVE-2026-15976 SGLang contains a RCE vulnerability when attempting to load model weights from a HuggingFace repository, specifically within the /update_weights_from_disk , where torch.load(..., weights_only=False) fallback enables pickle deserialization of .bin files. CVE-2026-15977 SGLang contains a credential leakage vulnerability in the /server_info endpoint, which returns API keys and SSL keyfile information when only the --admin-api-key is configured. CVE-2026-15978 SGLang contains a model weight exfiltration vulnerability when no API keys are configured, because SGLang will expose two endpoints that allow a remote attacker to trigger distributed weight broadcasting using NCCL and then triggering data transfer, attackers can exfiltrate all model weights. Impact If exploited, these vulnerabilities could allow an unauthenticated attacker to achieve remote code execution, exfiltrate model weights, or overwrite arbitrary files on the host machine running SGLang. Deployments that expose the affected interface to untrusted networks are at the highest risk of exploitation. Solution Until a patch is available, affected users should consider the following mitigations: Mitigations Restrict access to the service interfaces and ensure they are not exposed to untrusted networks. Implement network segmentation and access controls to prevent unauthorized interaction with the vulnerable endpoints. Change SGLANG_USE_PICKLE_IPC to "false" within environ.py . Disable endpoints not in use to remove potential attack vectors. The SGLang maintainers have begun addressing pickle deserialization vulnerabilities and are working to refactor the code base with msgpack to prevent deserialization issues such as CVE-2026-14890, but the SGLANG_USE_PICKLE_IPC defaults to true within the codebase at the time of writing. Acknowledgements Thanks to the reporter, Apoorv Dayal [apoorvdayal@outlook.com]. This document was written by Christopher Cullen. Vendor Information One or more vendors are listed for this advisory. Please reference the full report for more information. References https://github.com/sgl-project/sglang/security/advisories/GHSA-2wvm-gjg7-5jfm https://github.com/sgl-project/sglang/security/advisories/GHSA-h6rf-77vv-9mvj https://github.com/sgl-project/sglang/security/advisories/GHSA-wf98-gv64-5wrf https://github.com/sgl-project/sglang/security/advisories/GHSA-x7w5-h7rp-gfp9 https://github.com/sgl-project/sglang/security/advisories/GHSA-jx7q-p32r-7wx8 https://github.com/sgl-project/sglang/security/a… | GCVE Database | ||
| High | 8.8 | EPSS 0.8% | CVE-2026-58222Red Hat Enterprise Linux 10 · LDAP Injection High8.8EPSS 0.8%CVE Database V5CVE-2026-58222 CVE-2026-58222 is a security vulnerability in Samba Active Directory Domain Controller (AD DC) involving LDAP filter injection and improper authorization checks. It allows an authenticated low-privilege domain user to bypass normal access controls and disclose confidential Active Directory attributes. This information disclosure can lead to deriving sensitive authentication material, potentially enabling privilege escalation and complete domain compromise. Notably, in environments using Group Managed Service Accounts (gMSAs), attackers can extract sensitive keys to derive gMSA passwords offline. Red Hat Enterprise Linux standard installations are not affected as they do not ship the Samba AD DC role. A patch is available, and Red Hat manages remediation for this cloud-hosted service. EPSS 0.8%Vulnerability | CVE Database V5 | ||
| High | 8.3 | EPSS 0.4% | High8.3EPSS 0.4%CVE Database V5CVE-2026-65635 Improper Isolation or Compartmentalization vulnerability in malach-it boruta (Elixir.Boruta.Openid module) allows attackers to register OpenID Connect clients with administrative privileges through the dynamic client registration entry point. Boruta.Openid.register_client/3 forwards caller-supplied registration parameters to the administrative client creation path without a public/admin field-level allowlist, so an unauthenticated registrant can set security-sensitive attributes including supported grant types, authorized scopes, PKCE enforcement, public refresh and revocation behavior, token lifetimes, and signing settings. The library does not distinguish between metadata a public registrant is allowed to set and administrative controls that should require operator approval. This vulnerability is associated with program files lib/boruta/openid.ex and program routines 'Elixir.Boruta.Openid':register_client/3, 'Elixir.Boruta.Openid':parse_registration_params/2. This issue affects boruta from 2.3.0 before 2.3.7. | CVE Database V5 | ||
| High | 7.3 | EPSS 0.6% | High7.3EPSS 0.6%CVE Database V5CVE-2026-16527 CVE-2026-16527 is a vulnerability in the Performance Co-Pilot (PCP) pmproxy component of Red Hat Enterprise Linux 10 that allows unauthenticated remote attackers to bypass access controls by sending crafted requests to the /store endpoint. This flaw enables overwriting any PMDA metric, potentially leading to arbitrary code execution and full system takeover. | CVE Database V5 | ||
| –Not rated | – | Microsoft Security Blog As organizations move beyond AI experimentation, success will depend on how effectively they combine intelligence and trust. The same systems that amplify knowledge, accelerate decisions, and unlock new outcomes must also protect data, govern AI, and build resilience. In this next phase of transformation, security is not separate from innovation—it is an enabler that helps make responsible innovation possible at a faster pace. That starts with asking better questions—the kind that help organizations turn intelligence into action and trust into a foundation for progress. AI is changing how security decisions are made. Defenders now have access to more signals, insights, and analytical power than ever before. But better security does not start with more information. It starts with asking the right questions: What are we trying to protect? What risks matter most? What conditions need to be true? And what decisions do we need to make with confidence? That clarity matters because security is shaped by more than technology. The challenges organizations face rarely exist in isolation. They emerge across people, processes, technology, data, identities, and governance. Understanding those connections is what allows security teams to use platforms, AI, and automation to make better decisions under real-world conditions. Connect with Microsoft Security at Black Hat USA 2026 Security as a systems challenge Security has never been a single-layer challenge. Vulnerabilities can emerge across code, data, identities, and integrations, while exposure is often created at the intersections between them. Designing for security requires a systems mindset—understanding how these elements work together, where failure can occur, and what safeguards are needed so no single layer carries the burden alone. That is why defense in depth remains essential: layered controls, ongoing monitoring, mitigations, and risk management across the AI lifecycle help organizations reduce exposure while continuing to adapt. Agentic AI in cybersecurity Explore actionable takeaways ↗ This is especially important as AI becomes more embedded in how organizations operate. AI can help teams analyze vast amounts of information, identify patterns, and surface recommendations at a scale that was previously unthinkable. Those AI outputs still require oversight, governance, and human judgment, with clear accountability for how AI-generated insights are validated and used. But insight only creates value when it is grounded in the right context and connected to action. AI-generated insights still require validation, oversight, and resilience planning because AI systems can produce incomplete or inaccurate outputs. Clarity creates better decisions The most important security decisions start with a clear view of the risk, the level of control or visibility required, and the outcome the system is designed to achieve. When we optimize for capability over context, we miss how security decisions are actually made: through signals, expertise, validation, and judgment. This becomes even more important as AI expands what is possible. Better analysis can surface more insights, but better decisions still depend on understanding what matters most and applying the right context. That matters most when conditions are changing quickly, and teams need to act before every answer is certain. Threat intelligence offers a useful example. Defenders operate in environments defined by ambiguity, incomplete information, and rapidly changing conditions. Success rarely comes from a single source or signal. It comes from combining multiple forms of intelligence, applying expertise, validating assumptions, and connecting insights in ways that strengthen assurance. The lesson extends beyond threat intelligence. Different security objectives require different combinations of signals, analysis, and human judgment. Resilient decisions come from bringing those elements together thoughtfully, rather than relying on a… | Microsoft Security Blog | |||
| –Not rated | – | Kaspersky Security Blog Leveraging legitimate software is one of cybercriminals’ tactics of choice, with remote management tools ranking among their top tools. A recent example involves the remote administration utility ScreenConnect. It’s designed for IT support teams to troubleshoot systems and configure software seamlessly in the background. However, when weaponized by threat actors, ScreenConnect becomes a versatile attack vehicle used to harvest data, deploy malware, and move laterally across corporate networks. During a recent incident detected by Kaspersky Managed Detection and Response , our experts identified an attempt to use ScreenConnect in an attack. This allowed a detailed study of how attackers used this application in a large-scale malware distribution campaign. The following breakdown illustrates the mechanics of ScreenConnect-assisted attacks, and outlines key strategies to defend your organization against them. How ScreenConnect reaches target computers In the campaign analyzed by our experts, the attackers bundled ScreenConnect with legitimate free business software. They established a network of phishing websites to spoof popular tools, including OBS Studio, DS4Windows, DNS Jumper, Glary Utilities, Bandizip, Process Hacker, and others. These rogue websites featured high-quality designs that could be taken for the official pages, making them highly convincing to unsuspecting users. Once the victim clicks the download button for the software, an archive is downloaded to their computer that contains additional files alongside the requested application: A legitimately signed Microsoft executable ( exe ), renamed to match the expected application installer (for example, OBS-Studio-Installer.exe ) A malicious library named res.1033.dll An Assets directory containing installers for both ScreenConnect and the intended application Launching the renamed file disguised as the app installer triggers DLL sideloading of a malicious library. This library silently runs the ScreenConnect installation without restarting the system, while using the standard Windows installer to set up the software the user originally tried to install. The attackers used search engine optimization techniques to drive traffic to their fake websites. As a result, these malicious pages appeared at the top of search results for certain free software utilities on major search engines. Our experts discovered over 90 domain names translated into more than 10 different languages. While most of these websites targeted English, Russian, and Chinese speakers, several domains catered to German, French, Spanish, Arabic, and other regional audiences. A detailed analysis of the IP addresses and associated spoofed domains is available in our technical research article on Securelist, along with full indicators of compromise. Why the attackers exploited ScreenConnect In this campaign, attackers leveraged ScreenConnect to generate and execute malicious scripts on victim machines. These scripts served several key functions: they created exclusions for specific drives, directories, and processes within Windows Defender, disabled the User Account Control (UAC) security mechanism, and delivered and deployed AsyncRAT – a remote access Trojan. To maintain persistence, the scripts configured a Windows scheduled task to run the malicious code at preset intervals. AsyncRAT then established a connection with the attackers’ command-and-control server to receive further instructions. The primary objective of this campaign appears to be gaining unauthorized access to enterprise systems, likely to then resell it on cybercrime marketplaces. How to secure corporate infrastructure Although ScreenConnect in and of itself is a legitimate tool, its presence poses a security risk to corporate environments. Consequently, Kaspersky security solutions detect this application as not-a-virus:HEUR:RemoteAdmin.MSIL.ConnectWise.gen. Security teams should implement the following controls: Enforce strict applicatio… | Kaspersky Security Blog | |||
| –Not rated | – | Reddit BlueTeam A recent survey of 951 IT decision-makers reveals that AI-enhanced cyberattacks are already occurring, with 43% of organizations experiencing AI-generated phishing attacks and 37% encountering AI-powered malware. The report highlights an ongoing AI arms race between attackers using AI to automate and improve attacks and defenders adopting AI-based security tools. AI-generated phishing and social engineering are considered the most significant emerging cyber risks. Organizations are increasingly investing in AI threat detection, training, and controls to mitigate these risks. The threat landscape includes risks from internal AI misuse and data exposure. The consensus is that an AI-driven breach is a matter of when, not if. | Reddit BlueTeam | |||
| –Not rated | – | Bleeping Computer This security concern highlights the risks associated with AI agents operating with broad permissions, which can lead to significant security issues. The core issue is that AI agents improvise to complete tasks, and without strict identity and intent-based access controls, excessive permissions can cause unintended damage. The discussion emphasizes the importance of implementing least privilege principles and robust permission management to secure agentic AI systems. | Bleeping Computer | |||
| High | 8.5 | EPSS <0.1% | CVE-2026-44944open-iscsi · Incorrect Authorization Vulnerability High8.5EPSS <0.1%GCVE DatabaseCVE-2026-44944 CVE-2026-44944 is an incorrect authorization vulnerability in the open-iscsi component affecting the iscsiuio control socket. It allows unprivileged local users to bypass authentication controls. The vulnerability impacts multiple specific versions of open-iscsi used in Microsoft Azure Linux and iscsi-initiator-utils. No patch or remediation information is currently available. The issue is classified under CWE-863, indicating improper authorization. The severity is assessed as medium based on the available data. | GCVE Database | ||
| –Not rated | – | Reddit Cybersecurity This content discusses recurring security issues commonly observed in internet-facing infrastructure, such as exposed management interfaces, outdated software, weak TLS configurations, default credentials, and unintended public cloud services. It highlights that many organizations may struggle more with visibility of their assets than with fixing vulnerabilities. The information is derived from a Reddit post linking to a security service that scans domains for exposure and maps findings against UK Cyber Essentials controls. No specific vulnerability or exploit is detailed. | Reddit Cybersecurity | |||
| High | 8.2 | EPSS 0.6% | CVE-2026-58159Apache Traffic Server · Incorrect Authorization High8.2EPSS 0.6%CVE Database V5CVE-2026-58159 Apache Traffic Server can bypass IP access controls on UDS listeners and through ACL matching errors. This issue affects Apache Traffic Server: from 8.0.0 through 8.1.11, from 9.0.0 through 9.2.14, from 10.0.0 through 10.1.3. Users are recommended to upgrade to version 9.2.15 or 10.1.4, which fix the issue. | CVE Database V5 |
Page 29 of 77