π¨ CVE-2026-16908
IBM i 7.6, 7.5, 7.4, and 7.3 could allow a remote authenticated attacker to gain unauthorized access to arbitrary objects due to a path traversal vulnerability.
π@cveNotify
IBM i 7.6, 7.5, 7.4, and 7.3 could allow a remote authenticated attacker to gain unauthorized access to arbitrary objects due to a path traversal vulnerability.
π@cveNotify
Ibm
Security Bulletin: IBM i is Affected By Multiple SQL Vulnerabilities [CVE-2026-16908, CVE-2026-16967]
IBM i is vulnerable to multiple vulnerabilities [CVE-2026-16908, CVE-2026-16967] in SQL as described in the vulnerability details section.
π¨ CVE-2026-16961
IBM i 7.6, 7.5, and 7.4 s vulnerable to SQL injection. A remote attacker could send specially crafted SQL statements, which could allow the attacker to view, add, modify, or delete information in the back-end database.
π@cveNotify
IBM i 7.6, 7.5, and 7.4 s vulnerable to SQL injection. A remote attacker could send specially crafted SQL statements, which could allow the attacker to view, add, modify, or delete information in the back-end database.
π@cveNotify
Ibm
Security Bulletin: IBM i is Affected By SQL Injection Vulnerability in Db2 Mirror [CVE-2026-16961]
IBM i is vulnerable to Structure Query Language (SQL) injection as a result of processing specially crafted statements [CVE-2026-16961] in Db2 Mirror as described in the vulnerability details section.
π¨ CVE-2026-16967
IBM i 7.6, 7.5, 7.4, and 7.3 could allow a remote authenticated attacker to gain unauthorized access to system objects due to a time-of-check to time-of-use (TOCTOU) race condition involving symbolic links.
π@cveNotify
IBM i 7.6, 7.5, 7.4, and 7.3 could allow a remote authenticated attacker to gain unauthorized access to system objects due to a time-of-check to time-of-use (TOCTOU) race condition involving symbolic links.
π@cveNotify
Ibm
Security Bulletin: IBM i is Affected By Multiple SQL Vulnerabilities [CVE-2026-16908, CVE-2026-16967]
IBM i is vulnerable to multiple vulnerabilities [CVE-2026-16908, CVE-2026-16967] in SQL as described in the vulnerability details section.
π¨ CVE-2026-17029
IBM i 7.6, 7.5, 7.4, and 7.3 could allow a local attacker to execute arbitrary code due to an out-of-bounds write.
π@cveNotify
IBM i 7.6, 7.5, 7.4, and 7.3 could allow a local attacker to execute arbitrary code due to an out-of-bounds write.
π@cveNotify
Ibm
Security Bulletin: IBM i is Affected By Multiple Vulnerabilities in Java Secure Sockets Extension
IBM i is vulnerable to multiple vulnerabilities [CVE-2026-17029, CVE-2026-18511, CVE-2026-18068, CVE-2026-18086] in Java Secure Sockets Extension (JSSE) as described in the vulnerability details section.
π¨ CVE-2026-17045
IBM i 7.6, 7.5, 7.4, and 7.3 could allow a remote authenticated attacker to perform unauthorized operations and access sensitive information due to improper session management.
π@cveNotify
IBM i 7.6, 7.5, 7.4, and 7.3 could allow a remote authenticated attacker to perform unauthorized operations and access sensitive information due to improper session management.
π@cveNotify
Ibm
Security Bulletin: IBM i is Affected By Multiple Vulnerabilities in Digital Certificate Manager
IBM i is vulnerable to multiple vulnerabilities [CVE-2026-17088, CVE-2026-17075, CVE-2026-17071, CVE-2026-17069, CVE-2026-17045, CVE-2026-17043] in Digital Certificate Manager (DCM) as described in the vulnerability details section.
π¨ CVE-2026-17069
IBM i 7.6, 7.5, 7.4, and 7.3 could allow a remote authenticated attacker to bypass security restrictions due to improper validation of anti-CSRF tokens.
π@cveNotify
IBM i 7.6, 7.5, 7.4, and 7.3 could allow a remote authenticated attacker to bypass security restrictions due to improper validation of anti-CSRF tokens.
π@cveNotify
Ibm
Security Bulletin: IBM i is Affected By Multiple Vulnerabilities in Digital Certificate Manager
IBM i is vulnerable to multiple vulnerabilities [CVE-2026-17088, CVE-2026-17075, CVE-2026-17071, CVE-2026-17069, CVE-2026-17045, CVE-2026-17043] in Digital Certificate Manager (DCM) as described in the vulnerability details section.
π¨ CVE-2026-17199
IBM i 7.6, 7.5, 7.4, and 7.3 could allow a remote attacker to cause a denial of service due to unbounded resource allocation.
π@cveNotify
IBM i 7.6, 7.5, 7.4, and 7.3 could allow a remote attacker to cause a denial of service due to unbounded resource allocation.
π@cveNotify
Ibm
Security Bulletin: IBM i is Affected By Multiple Vulnerabilities in Host Servers
IBM i is vulnerable to multiple vulnerabilities [CVE-2026-17223, CVE-2026-17206, CVE-2026-17208, CVE-2026-16929, CVE-2026-17004, CVE-2026-18846, CVE-2026-17197, CVE-2026-17217, CVE-2026-17199, CVE-2026-17229, CVE-2026-16982] in host servers, and a bufferβ¦
π¨ CVE-2026-17206
IBM i 7.6, 7.5, 7.4, and 7.3 could allow a remote attacker to execute arbitrary code due to a buffer overflow.
π@cveNotify
IBM i 7.6, 7.5, 7.4, and 7.3 could allow a remote attacker to execute arbitrary code due to a buffer overflow.
π@cveNotify
Ibm
Security Bulletin: IBM i is Affected By Multiple Vulnerabilities in Host Servers
IBM i is vulnerable to multiple vulnerabilities [CVE-2026-17223, CVE-2026-17206, CVE-2026-17208, CVE-2026-16929, CVE-2026-17004, CVE-2026-18846, CVE-2026-17197, CVE-2026-17217, CVE-2026-17199, CVE-2026-17229, CVE-2026-16982] in host servers, and a bufferβ¦
π¨ CVE-2026-17223
IBM i 7.6, 7.5, 7.4, and 7.3 could allow a remote authenticated attacker to execute arbitrary code due to a buffer overflow.
π@cveNotify
IBM i 7.6, 7.5, 7.4, and 7.3 could allow a remote authenticated attacker to execute arbitrary code due to a buffer overflow.
π@cveNotify
Ibm
Security Bulletin: IBM i is Affected By Multiple Vulnerabilities in Host Servers
IBM i is vulnerable to multiple vulnerabilities [CVE-2026-17223, CVE-2026-17206, CVE-2026-17208, CVE-2026-16929, CVE-2026-17004, CVE-2026-18846, CVE-2026-17197, CVE-2026-17217, CVE-2026-17199, CVE-2026-17229, CVE-2026-16982] in host servers, and a bufferβ¦
π¨ CVE-2026-17229
IBM i 7.6, 7.5, 7.4, and 7.3 could allow a remote attacker to cause a denial of service due to an infinite loop.
π@cveNotify
IBM i 7.6, 7.5, 7.4, and 7.3 could allow a remote attacker to cause a denial of service due to an infinite loop.
π@cveNotify
Ibm
Security Bulletin: IBM i is Affected By Multiple Vulnerabilities in Host Servers
IBM i is vulnerable to multiple vulnerabilities [CVE-2026-17223, CVE-2026-17206, CVE-2026-17208, CVE-2026-16929, CVE-2026-17004, CVE-2026-18846, CVE-2026-17197, CVE-2026-17217, CVE-2026-17199, CVE-2026-17229, CVE-2026-16982] in host servers, and a bufferβ¦
π¨ CVE-2026-18846
IBM i 7.6, 7.5, 7.4, and 7.3 s vulnerable to a buffer overflow from improperly validating client data. By sending malformed requests to one of the host servers, a remote attacker could leverage this vulnerability to cause a denial-of-server (DoS) for that server.
π@cveNotify
IBM i 7.6, 7.5, 7.4, and 7.3 s vulnerable to a buffer overflow from improperly validating client data. By sending malformed requests to one of the host servers, a remote attacker could leverage this vulnerability to cause a denial-of-server (DoS) for that server.
π@cveNotify
Ibm
Security Bulletin: IBM i is Affected By Multiple Vulnerabilities in Host Servers
IBM i is vulnerable to multiple vulnerabilities [CVE-2026-17223, CVE-2026-17206, CVE-2026-17208, CVE-2026-16929, CVE-2026-17004, CVE-2026-18846, CVE-2026-17197, CVE-2026-17217, CVE-2026-17199, CVE-2026-17229, CVE-2026-16982] in host servers, and a bufferβ¦
π¨ CVE-2025-62593
Ray is an AI compute engine. Prior to version 2.52.0, developers working with Ray as a development tool can be exploited via a critical RCE vulnerability exploitable via Firefox and Safari. This vulnerability is due to an insufficient guard against browser-based attacks, as the current defense uses the User-Agent header starting with the string "Mozilla" as a defense mechanism. This defense is insufficient as the fetch specification allows the User-Agent header to be modified. Combined with a DNS rebinding attack against the browser, and this vulnerability is exploitable against a developer running Ray who inadvertently visits a malicious website, or is served a malicious advertisement (malvertising). This issue has been patched in version 2.52.0.
π@cveNotify
Ray is an AI compute engine. Prior to version 2.52.0, developers working with Ray as a development tool can be exploited via a critical RCE vulnerability exploitable via Firefox and Safari. This vulnerability is due to an insufficient guard against browser-based attacks, as the current defense uses the User-Agent header starting with the string "Mozilla" as a defense mechanism. This defense is insufficient as the fetch specification allows the User-Agent header to be modified. Combined with a DNS rebinding attack against the browser, and this vulnerability is exploitable against a developer running Ray who inadvertently visits a malicious website, or is served a malicious advertisement (malvertising). This issue has been patched in version 2.52.0.
π@cveNotify
π¨ CVE-2026-11788
A flaw was found in 389 Directory Server. The dereference control plugin does not check for allocation failure before using a BER structure, allowing an unauthenticated remote attacker to crash the LDAP server when the system is under memory pressure.
π@cveNotify
A flaw was found in 389 Directory Server. The dereference control plugin does not check for allocation failure before using a BER structure, allowing an unauthenticated remote attacker to crash the LDAP server when the system is under memory pressure.
π@cveNotify
π¨ CVE-2026-11717
An authentication bypass vulnerability exists in the generic opaque token validation path (validateOpaqueToken) of googleapis/mcp-toolbox.
When verifying an unparsed opaque token via an OAuth 2.0 introspection endpoint (RFC 7662), the toolbox decodes the response into an introspectResp struct where the Active field is declared as a pointer to a boolean (*bool). The code only explicitly rejects a token if the response contains a populated active field set to false (if introspectResp.Active != nil && !*introspectResp.Active). If an introspection endpoint responds with a payload that completely omits the mandatory active key, the internal variable remains nil, causing the conditional check to short-circuit. As a result, Toolbox accepts authorization tokens missing the "active" field, granting access to protected tools and underlying data sources.
π@cveNotify
An authentication bypass vulnerability exists in the generic opaque token validation path (validateOpaqueToken) of googleapis/mcp-toolbox.
When verifying an unparsed opaque token via an OAuth 2.0 introspection endpoint (RFC 7662), the toolbox decodes the response into an introspectResp struct where the Active field is declared as a pointer to a boolean (*bool). The code only explicitly rejects a token if the response contains a populated active field set to false (if introspectResp.Active != nil && !*introspectResp.Active). If an introspection endpoint responds with a payload that completely omits the mandatory active key, the internal variable remains nil, causing the conditional check to short-circuit. As a result, Toolbox accepts authorization tokens missing the "active" field, granting access to protected tools and underlying data sources.
π@cveNotify
GitHub
fix(auth): separate Google and Generic MCP OAuth verification by duwenxin99 Β· Pull Request #3341 Β· googleapis/mcp-toolbox
enforce "active" field checks in generic OAuth
support MCP auth separately in "google" type authService because Google OAuth tokeninfo endpoint returns non-stand...
support MCP auth separately in "google" type authService because Google OAuth tokeninfo endpoint returns non-stand...
π¨ CVE-2026-11718
An authentication bypass vulnerability exists in the generic opaque token validation path (validateOpaqueToken) of googleapis/mcp-toolbox.
When the toolbox validates an opaque token via an OAuth 2.0 introspection endpoint (RFC 7662), it decodes the response into an introspectResp struct. However, the subsequent claim-checking logic (validateClaims) evaluates the issuer condition as if a.issuer != "" && iss != "". If the external OAuth provider's introspection response omits the optional iss (issuer) field completely, the variable iss defaults to an empty string. This causes the conditional block to evaluate to false and be skipped silently. Consequently, the application accepts tokens issued by unauthorized or unintended third-party identity providers.
π@cveNotify
An authentication bypass vulnerability exists in the generic opaque token validation path (validateOpaqueToken) of googleapis/mcp-toolbox.
When the toolbox validates an opaque token via an OAuth 2.0 introspection endpoint (RFC 7662), it decodes the response into an introspectResp struct. However, the subsequent claim-checking logic (validateClaims) evaluates the issuer condition as if a.issuer != "" && iss != "". If the external OAuth provider's introspection response omits the optional iss (issuer) field completely, the variable iss defaults to an empty string. This causes the conditional block to evaluate to false and be skipped silently. Consequently, the application accepts tokens issued by unauthorized or unintended third-party identity providers.
π@cveNotify
GitHub
fix(auth/generic): enforce issuer presence in opaque token validation by duwenxin99 Β· Pull Request #3360 Β· googleapis/mcp-toolbox
Reported by: HaoNH, Red Team Leader at VinCSS.
π¨ CVE-2026-11719
An authenticated authorization bypass vulnerability exists in MCP Toolbox for Databases due to missing scope enforcement across older protocol handlers.
While the 2025-11-25 protocol version handler correctly enforces per-tool restrictions defined by scopesRequired, older supported protocol versions (2025-06-18, 2025-03-26, and 2024-11-05) omit this check. An authenticated client with low-privilege tokens (e.g., read) can bypass the intended per-tool scope restrictions and execute high-privilege tools (e.g., admin) simply by specifying an older protocol version in the MCP-Protocol-Version header, or by omitting the header entirely (which causes the server to default to the vulnerable 2024-11-05 handler).
π@cveNotify
An authenticated authorization bypass vulnerability exists in MCP Toolbox for Databases due to missing scope enforcement across older protocol handlers.
While the 2025-11-25 protocol version handler correctly enforces per-tool restrictions defined by scopesRequired, older supported protocol versions (2025-06-18, 2025-03-26, and 2024-11-05) omit this check. An authenticated client with low-privilege tokens (e.g., read) can bypass the intended per-tool scope restrictions and execute high-privilege tools (e.g., admin) simply by specifying an older protocol version in the MCP-Protocol-Version header, or by omitting the header entirely (which causes the server to default to the vulnerable 2024-11-05 handler).
π@cveNotify
GitHub
feat(auth): implement MCP auth tool-level scopes validation by duwenxin99 Β· Pull Request #3049 Β· googleapis/mcp-toolbox
MCP Toolbox for Databases is an open source MCP server for databases. - feat(auth): implement MCP auth tool-level scopes validation by duwenxin99 Β· Pull Request #3049 Β· googleapis/mcp-toolbox
π¨ CVE-2019-25758
Joomla! Component vBizz 1.0.7 contains an unrestricted file upload vulnerability that allows authenticated attackers to upload arbitrary PHP files by submitting malicious files through the profile_pic parameter. Attackers can upload PHP files via POST requests to the employee view endpoint and execute them from the uploads directory to achieve remote code execution.
π@cveNotify
Joomla! Component vBizz 1.0.7 contains an unrestricted file upload vulnerability that allows authenticated attackers to upload arbitrary PHP files by submitting malicious files through the profile_pic parameter. Attackers can upload PHP files via POST requests to the employee view endpoint and execute them from the uploads directory to achieve remote code execution.
π@cveNotify
WDMtech
Top Web, Mobile, Custom Software Development Company
WDMtech is the best software development company in India. We deliver web software & mobile app development solutions for every startup and big brand.
π¨ CVE-2019-25759
Joomla! Component vBizz 1.0.7 contains an SQL injection vulnerability that allows authenticated attackers to execute arbitrary SQL queries by injecting malicious code through the payid parameter. Attackers can submit POST requests to the employee management interface with crafted payid array values containing SQL commands to extract sensitive database information including version and database names.
π@cveNotify
Joomla! Component vBizz 1.0.7 contains an SQL injection vulnerability that allows authenticated attackers to execute arbitrary SQL queries by injecting malicious code through the payid parameter. Attackers can submit POST requests to the employee management interface with crafted payid array values containing SQL commands to extract sensitive database information including version and database names.
π@cveNotify
WDMtech
Top Web, Mobile, Custom Software Development Company
WDMtech is the best software development company in India. We deliver web software & mobile app development solutions for every startup and big brand.
π¨ CVE-2026-17523
A flaw was found in the Linux kernel in net/can/bcm.c in can: bcm, where an unprivileged local user can exploit this vulnerability to execute arbitrary code within the kernel, which leads to a local privilege escalation (LPE). This allows the attacker to gain root privileges and take full control of the affected system.
π@cveNotify
A flaw was found in the Linux kernel in net/can/bcm.c in can: bcm, where an unprivileged local user can exploit this vulnerability to execute arbitrary code within the kernel, which leads to a local privilege escalation (LPE). This allows the attacker to gain root privileges and take full control of the affected system.
π@cveNotify
π¨ CVE-2026-11770
A flaw was found in 389 Directory Server. An unauthenticated remote attacker can inject LDAP search filters into the CleanAllRUV replication status-check extended operation. Because the handler performs the search against cn=config with elevated replication plugin privileges and returns a boolean match result, the attacker can extract sensitive server configuration metadata, including replication bind DNs and password storage scheme information.
π@cveNotify
A flaw was found in 389 Directory Server. An unauthenticated remote attacker can inject LDAP search filters into the CleanAllRUV replication status-check extended operation. Because the handler performs the search against cn=config with elevated replication plugin privileges and returns a boolean match result, the attacker can extract sensitive server configuration metadata, including replication bind DNs and password storage scheme information.
π@cveNotify
π¨ CVE-2026-15722
A stack buffer overflow flaw was found in 389 Directory Server (389-ds-base). The get_ruvelement_from_berval() function in repl5_ruv.c copies digit characters from a network-supplied RUV berval into a fixed 16-byte stack buffer without bounds checking. A remote unauthenticated attacker can crash the LDAP server by sending a crafted StartNSDS50ReplicationRequest extended operation containing a replica ID field with more than 16 digit characters. The overflow occurs during payload decoding, before any authorization check. Stack protectors limit impact to denial of service.
π@cveNotify
A stack buffer overflow flaw was found in 389 Directory Server (389-ds-base). The get_ruvelement_from_berval() function in repl5_ruv.c copies digit characters from a network-supplied RUV berval into a fixed 16-byte stack buffer without bounds checking. A remote unauthenticated attacker can crash the LDAP server by sending a crafted StartNSDS50ReplicationRequest extended operation containing a replica ID field with more than 16 digit characters. The overflow occurs during payload decoding, before any authorization check. Stack protectors limit impact to denial of service.
π@cveNotify