NVD disclosure day
CVE-2026-123966
Halo Surface Signal: 4 out of 5 — likely to be public-facing.
A critical vulnerability in Tenda routers allows remote attackers to cause a heap-based buffer overflow, potentially leading to system compromise. The exploit has been publicly disclosed, making it a significant concern for network security if the affected technology is reachable. It is important to verify if this rout
CVE-2026-120984
Halo Surface Signal: 3 out of 5 — possibly public-facing.
A flaw in Keycloak's client management component allows an authenticated attacker with specific permissions to upload a malicious JavaScript policy. This policy can execute on the server during authorization requests, potentially leading to arbitrary code execution and system compromise.
CVE-2026-122041
Halo Surface Signal: 4 out of 5 — likely to be public-facing.
A critical vulnerability in a WordPress plugin allows unauthenticated attackers to delete arbitrary attachments due to a missing authorization check. This could lead to the loss of important media and potential denial of service for businesses relying on this functionality.
CVE-2026-119075
Halo Surface Signal: 5 out of 5 — more likely to be public-facing.
A vulnerability in the Registration Form for WooCommerce plugin allows unauthenticated attackers to escalate privileges to Administrator, potentially leading to full site takeover. This is possible by manipulating user role assignment during checkout, bypassing validation checks. Confirmation of the plugin's use and th
CVE-2026-118066
Halo Surface Signal: 5 out of 5 — more likely to be public-facing.
A vulnerability in the Appointment Booking Plugin for WordPress allows unauthenticated attackers to bypass authentication and take over customer accounts. This could expose sensitive booking and personal information, granting attackers unauthorized access to customer data.
CVE-2026-104014
Halo Surface Signal: 4 out of 5 — likely to be public-facing.
A vulnerability in the Naimur Email OTP Verification for WooCommerce WordPress plugin allows unauthenticated attackers to bypass authentication and take over user accounts. This occurs if a user previously initiated but did not complete a password reset. Attackers only need the victim's email and a nonce to overwrite t
CVE-2026-121491
Halo Surface Signal: 4 out of 5 — likely to be public-facing.
A vulnerability in the Fiber Admin WordPress plugin could allow unauthenticated attackers to execute arbitrary code. This occurs when its custom error page is enabled and attackers can exploit a race condition to write malicious code to a PHP file. The potential impact includes unauthorized code execution.
CVE-2026-121379
Halo Surface Signal: 4 out of 5 — likely to be public-facing.
A vulnerability in the Tournamatch WordPress plugin allows low-privileged users to delete arbitrary server files, potentially leading to a full website takeover. This issue arises because the plugin does not properly validate file paths when deleting old images during an upload. If reachable, this could impact website
CVE-2026-18838
Halo Surface Signal: 5 out of 5 — more likely to be public-facing.
A vulnerability in IBM API Connect allows remote attackers to obtain sensitive information and modify API configurations by not sufficiently verifying identity information in requests. This could permit an attacker to impersonate another user if the technology is reachable.
CVE-2026-18836
Halo Surface Signal: 5 out of 5 — more likely to be public-facing.
IBM API Connect is vulnerable to server-side request forgery, potentially allowing attackers to obtain sensitive information by making the system send requests to unintended destinations. This critical vulnerability affects internet-facing API management, and its relevance and potential exposure should be assessed.
CVE-2026-18535
Halo Surface Signal: 4 out of 5 — likely to be public-facing.
IBM API Connect has critical vulnerabilities that could allow attackers to disrupt services or access sensitive information. The issue arises from improper handling of regular expressions and wildcard query operators, potentially impacting external-facing APIs. Confirmation of relevance and exposure is necessary to und
CVE-2026-17410
Halo Surface Signal: 4 out of 5 — likely to be public-facing.
A critical vulnerability in IBM API Connect allows authenticated attackers to access and modify other tenants' portal data due to improper argument delimiter handling. This could lead to unauthorized viewing or alteration of sensitive customer information, impacting API management functions. Confirming the relevance an
CVE-2026-17409
Halo Surface Signal: 5 out of 5 — more likely to be public-facing.
IBM API Connect has a vulnerability due to improper handling of case sensitivity, which could allow remote attackers to execute unauthorized administrative operations and obtain sensitive information. This issue is relevant because the product is designed for external exposure as an API gateway.
CVE-2026-17408
Halo Surface Signal: 5 out of 5 — more likely to be public-facing.
IBM API Connect has a critical vulnerability that allows remote attackers to execute arbitrary code due to improper OS command handling. If reachable, this could impact system confidentiality, integrity, and availability. Confirming its use and exposure is crucial.
CVE-2026-17403
Halo Surface Signal: 4 out of 5 — likely to be public-facing.
IBM API Connect contains hard-coded credentials that a remote attacker could exploit to gain full administrative control. This vulnerability could impact the integrity and availability of the API management service. Exploiting this issue requires network access and could lead to unauthorized administrative privileges.
CVE-2026-17402
Halo Surface Signal: 4 out of 5 — likely to be public-facing.
A critical vulnerability in IBM API Connect allows authenticated attackers to run arbitrary commands on the host system due to improper handling of user input. This could lead to a compromise of the underlying host, impacting API management services.
CVE-2026-17399
Halo Surface Signal: 4 out of 5 — likely to be public-facing.
A critical vulnerability exists in IBM API Connect where insufficient validation of uploaded content can allow a remote, authenticated attacker to execute arbitrary code. This could lead to compromise of server integrity and data security.
CVE-2026-17396
Halo Surface Signal: 4 out of 5 — likely to be public-facing.
A SQL injection vulnerability in IBM API Connect could allow a remote attacker with credentials to obtain sensitive information. This may affect data security and business operations if relevant deployments are reachable.
CVE-2026-17394
Halo Surface Signal: 4 out of 5 — likely to be public-facing.
IBM API Connect contains a vulnerability where an authenticated attacker can modify object attributes, potentially exposing sensitive information. This flaw could allow a user-supplied value to alter access-related settings that should be system-controlled. Given API Connect's role in managing external-facing APIs, thi
CVE-2026-17392
Halo Surface Signal: 4 out of 5 — likely to be public-facing.
A critical vulnerability in IBM API Connect allows an authenticated user to gain unauthorized administrative access to other tenants due to LDAP injection. This occurs when user-supplied input is not properly neutralized in directory queries, potentially altering them to grant broader permissions. This could impact API
CVE-2026-17360
Halo Surface Signal: 5 out of 5 — more likely to be public-facing.
IBM API Connect has a critical vulnerability due to hard-coded credentials that could allow remote attackers to gain full administrative control. This issue is relevant because IBM API Connect is often deployed at the network edge and exposed externally for managing public-facing API traffic. The potential for complete
CVE-2026-17359
Halo Surface Signal: 4 out of 5 — likely to be public-facing.
IBM API Connect has a critical vulnerability where an authenticated attacker can execute arbitrary code by influencing the product's code generation. This could impact system data and service behavior if the technology is exposed.
CVE-2026-17354
Halo Surface Signal: 4 out of 5 — likely to be public-facing.
A path traversal vulnerability in IBM API Connect allows authenticated attackers to write files to arbitrary locations. If reachable, this could impact system integrity by overwriting critical files. The exposure is classified as external, meaning network-based attacks are possible.
CVE-2026-17353
Halo Surface Signal: 4 out of 5 — likely to be public-facing.
A critical vulnerability in IBM API Connect could allow authenticated users to access sensitive information and bypass security controls by exploiting a server-side request forgery flaw. This issue could potentially expose confidential data and undermine access controls within the managed API environment.
CVE-2026-17344
Halo Surface Signal: 5 out of 5 — more likely to be public-facing.
A server-side request forgery vulnerability in IBM API Connect could allow unauthenticated attackers to access sensitive information by tricking the service into making requests to unintended destinations. This affects systems that are publicly accessible, potentially exposing internal resources or data. Confirming the
CVE-2026-17342
Halo Surface Signal: 4 out of 5 — likely to be public-facing.
IBM API Connect is vulnerable to arbitrary code execution due to improper code generation controls. An authenticated attacker could exploit this by sending a malicious request, potentially compromising the system. This issue affects how APIs are managed and secured.
CVE-2026-17340
Halo Surface Signal: 5 out of 5 — more likely to be public-facing.
A path traversal vulnerability in IBM API Connect could enable remote attackers to execute arbitrary code. Exploitation requires network access and could impact system confidentiality, integrity, and availability. This vulnerability is classified as external and is very likely to be reachable.
CVE-2026-17339
Halo Surface Signal: 4 out of 5 — likely to be public-facing.
A path traversal vulnerability in IBM API Connect could allow an authenticated user to access or delete resources from other tenants, posing a risk of unauthorized data exposure or loss. Its relevance depends on your organization's use of this product and its exposure.
CVE-2026-17338
Halo Surface Signal: 4 out of 5 — likely to be public-facing.
A critical vulnerability in IBM API Connect allows authenticated users to access sensitive information due to broken object-level authorization. This means an attacker with valid credentials could potentially bypass security controls to obtain unauthorized data, impacting the confidentiality of managed APIs and associa
CVE-2026-17336
Halo Surface Signal: 4 out of 5 — likely to be public-facing.
A vulnerability in IBM API Connect could allow a remote authenticated attacker to execute arbitrary SQL commands by improperly neutralizing special elements in SQL commands, potentially impacting data integrity and service availability.
CVE-2026-17329
Halo Surface Signal: 5 out of 5 — more likely to be public-facing.
A critical vulnerability in IBM API Connect allows remote attackers to obtain sensitive information due to improper validation of endpoint URLs. This could expose sensitive data managed by the API gateway. You should care because this issue could impact your organization's data security.
CVE-2026-17313
Halo Surface Signal: 5 out of 5 — more likely to be public-facing.
IBM API Connect has an authentication bypass vulnerability allowing remote attackers to access sensitive information and control gateway configurations. This could lead to unauthorized access and compromise of API management infrastructure when reachable. Confirming the presence and exposure of this technology within y
CVE-2026-17301
Halo Surface Signal: 5 out of 5 — more likely to be public-facing.
An issue in IBM API Connect allows unauthenticated attackers to bypass authentication by exploiting improper cryptographic signature verification. This vulnerability could grant unauthorized access to API resources, making it critical for securing external-facing API management.
CVE-2026-17299
Halo Surface Signal: 4 out of 5 — likely to be public-facing.
IBM API Connect has a vulnerability where it does not sufficiently restrict externally referenced content in submitted definitions, potentially allowing authenticated attackers to perform arbitrary file reads and server-side request forgery. This means retrieved content could be returned to the attacker, posing a risk
CVE-2026-17298
Halo Surface Signal: 4 out of 5 — likely to be public-facing.
A server-side request forgery vulnerability in IBM API Connect may allow a remote authenticated attacker to access sensitive information. This could occur if an attacker crafts a request that causes the server to make unintended external requests. You should care because this could expose confidential data within your
CVE-2026-17297
Halo Surface Signal: 4 out of 5 — likely to be public-facing.
An open redirect vulnerability in IBM API Connect may allow a remote attacker to perform an account takeover. This occurs because the redirect address used during sign-in is not sufficiently validated, potentially allowing authentication results to be sent to an attacker-controlled location. Given that API Connect is t
CVE-2026-17296
Halo Surface Signal: 4 out of 5 — likely to be public-facing.
A server-side request forgery vulnerability in IBM API Connect could allow an authenticated attacker to obtain sensitive information. This occurs when the vulnerable system can be tricked into making unintended requests, potentially exposing data. Organizations using IBM API Connect should determine if their instances
CVE-2026-17292
Halo Surface Signal: 4 out of 5 — likely to be public-facing.
A critical vulnerability in IBM API Connect allows authenticated attackers to take over other organizations by bypassing incomplete access checks on organization objects. This could lead to unauthorized control over unrelated parts of the API management platform.
CVE-2026-17278
Halo Surface Signal: 5 out of 5 — more likely to be public-facing.
IBM API Connect has a critical vulnerability where improper authentication allows unauthorized remote access to sensitive API catalog and runtime configuration data. An attacker can exploit this by impersonating a trusted party due to insufficient verification of client-provided information, potentially exposing intern
CVE-2026-17239
Halo Surface Signal: 4 out of 5 — likely to be public-facing.
A path traversal vulnerability in IBM API Connect could allow an authenticated remote attacker to execute arbitrary code. This could impact the integrity and availability of the API Connect service and potentially lead to unauthorized access to underlying system resources or data.
CVE-2026-17158
Halo Surface Signal: 4 out of 5 — likely to be public-facing.
A critical vulnerability exists in IBM API Connect, allowing a remote authenticated attacker to gain elevated privileges due to improper authentication. This could impact the integrity and availability of managed services. Confirming the use and exposure of this technology is important for understanding potential risks
CVE-2026-17150
Halo Surface Signal: 4 out of 5 — likely to be public-facing.
IBM API Connect has a critical vulnerability where insufficient validation of uploaded custom modules allows authenticated attackers to execute arbitrary code and access sensitive information from other tenants, posing a risk to data confidentiality and system integrity.
CVE-2026-17147
Halo Surface Signal: 4 out of 5 — likely to be public-facing.
A path traversal vulnerability in IBM API Connect could allow a remote authenticated attacker to execute arbitrary code and perform unauthorized administrative actions. This issue affects specific versions of the API Connect software, a platform used for managing and securing APIs. The primary concern is to confirm if
CVE-2026-17146
Halo Surface Signal: 4 out of 5 — likely to be public-facing.
IBM API Connect has a vulnerability allowing authenticated attackers to execute JavaScript and access sensitive data due to improper input validation. This could impact API management services, leading to unauthorized access and information disclosure. Uncertainty exists regarding specific exploitation details and impa
CVE-2026-17134
Halo Surface Signal: 4 out of 5 — likely to be public-facing.
IBM API Connect has a SQL injection vulnerability that could allow an authenticated attacker to run unauthorized SQL commands, potentially leading to data compromise. This issue affects systems that manage and expose APIs, and it is important to confirm if your deployed instances are relevant and potentially exposed.
CVE-2026-17132
Halo Surface Signal: 4 out of 5 — likely to be public-facing.
IBM API Connect has a critical SQL injection vulnerability that allows remote authenticated attackers to execute arbitrary SQL commands due to improper neutralization of special elements. This could impact data integrity and system availability, necessitating confirmation of affected versions and exposure in your envir
CVE-2026-17131
Halo Surface Signal: 4 out of 5 — likely to be public-facing.
A critical vulnerability in IBM API Connect may allow a remote attacker to obtain sensitive information through server-side request forgery by bypassing outbound request restrictions, potentially causing the server to contact unintended destinations and return responses.
CVE-2026-17117
Halo Surface Signal: 4 out of 5 — likely to be public-facing.
A critical vulnerability in IBM API Connect could allow an authenticated attacker to execute arbitrary code by improperly modifying object attributes. This could impact system integrity and availability if exploited.
CVE-2026-17066
Halo Surface Signal: 4 out of 5 — likely to be public-facing.
A vulnerability in IBM API Connect could allow an authenticated attacker to access or modify data belonging to other tenants due to missing authorization checks. This could lead to unauthorized exposure or alteration of sensitive information.
CVE-2026-17049
Halo Surface Signal: 4 out of 5 — likely to be public-facing.
A critical vulnerability in IBM API Connect, a platform for managing APIs, allows authenticated attackers to bypass authorization through user-controlled keys. This could lead to unauthorized access to sensitive information and modification of arbitrary documents. Security teams should identify and assess affected inst
CVE-2026-16920
Halo Surface Signal: 4 out of 5 — likely to be public-facing.
A critical confused deputy vulnerability in IBM API Connect may allow a remote authenticated attacker to bypass security restrictions. This could impact the confidentiality, integrity, and availability of services. It is uncertain if this technology is used within our environment or its exposure.
CVE-2026-16918
Halo Surface Signal: 4 out of 5 — likely to be public-facing.
IBM API Connect has a critical server-side request forgery vulnerability allowing remote attackers to access internal network resources. This impacts the security of the API management solution when it's exposed to the network, potentially leading to unauthorized access within the internal network.
CVE-2026-16884
Halo Surface Signal: 5 out of 5 — more likely to be public-facing.
IBM API Connect has a vulnerability allowing remote attackers to obtain sensitive information through XML external entity injection. This issue is critical because IBM API Connect manages external-facing APIs, potentially exposing internal data if exploited by crafted requests. Confirming reachability and business crit
CVE-2026-16720
Halo Surface Signal: 5 out of 5 — more likely to be public-facing.
A critical vulnerability in IBM API Connect allows remote attackers to obtain access tokens for other users due to improper authentication, potentially enabling user impersonation. This means an attacker could assume another user's identity. This is a significant risk as IBM API Connect manages APIs and acts as an iden
CVE-2026-19803
Halo Surface Signal: 5 out of 5 — more likely to be public-facing.
The Printcart Store plugin for WordPress is vulnerable to arbitrary file uploads, enabling unauthenticated attackers to execute arbitrary code on the server if a specific configuration is active. This vulnerability requires a public-facing component and a readily obtainable security token, posing a risk of remote code
CVE-2026-17362
Halo Surface Signal: 5 out of 5 — more likely to be public-facing.
IBM API Connect has a critical vulnerability due to missing authorization, allowing remote attackers to create, modify, or delete tenants. This could impact the integrity and availability of managed APIs and services if the technology is in use and reachable. Further analysis is needed to confirm relevance and assess e
CVE-2026-123218
Halo Surface Signal: 4 out of 5 — likely to be public-facing.
A vulnerability exists in IBM Aspera Faspex that could allow an authorized user to gain full administrative privileges by crafting a specific message. This could enable unauthorized access to administrative controls and potential data compromise, as the platform is often exposed to the public internet.
CVE-2026-93754
Halo Surface Signal: 4 out of 5 — likely to be public-facing.
A critical vulnerability exists in the payever – WooCommerce Gateway plugin for WordPress, allowing unauthenticated attackers to upload and execute arbitrary files. This could lead to remote code execution and compromise of the website. The vulnerability is due to unprotected API callbacks that accept file uploads with