1384 matches found
PT-2026-62123
In Zephyr's Bluetooth Mesh PB-ADV provisioning bearer subsys/bluetooth/mesh/pb adv.c, prov msg recv rescheduled the provisioning protocol watchdog timer unconditionally at the top of the function, before the FCS check and before the ADV LINK INVALID check. Once a provisioning attempt fails, prov...
tomcat9 security update
1:9.0.117-2 - Resolves: RHEL-185571 Remove tomcat clustering JAR from RPM builds 1:9.0.117-1 - Resolves: RHEL-150720 Tomcat: Certificate revocation bypass due to improper OCSP response validation CVE-2026-24734 - Resolves: Tomcat: OCSP checks sometimes soft-fail with FFM even when soft-fail is...
Oracle Linux 10 : tomcat9 (ELSA-2026-36790)
The remote Oracle Linux 10 host has packages installed that are affected by multiple vulnerabilities as referenced in the ELSA-2026-36790 advisory. - Resolves: RHEL-150720 Tomcat: Certificate revocation bypass due to improper OCSP response validation CVE-2026-24734 - Resolves: Tomcat: OCSP checks...
CVE-2026-55550
NextCRM is open-source customer relationship management CRM software. The CRM product catalog is an organization-wide business object. Normal application server actions restrict product creation, update, and deletion to manager and admin roles. However, in version 0.12.1, the MCP product tools...
CVE-2026-55544 NextCRM has BOLA/IDOR in MCP Campaign Tools that Allows Cross-User Campaign Disclosure and Tampering
NextCRM is open-source customer relationship management CRM software. In version 0.12.1, the MCP campaign tools expose campaign read and write operations over the network using user-generated Bearer API tokens nxtc.... The application has an authorization model that restricts normal users to...
CVE-2026-55544 NextCRM has BOLA/IDOR in MCP Campaign Tools that Allows Cross-User Campaign Disclosure and Tampering
NextCRM is open-source customer relationship management CRM software. In version 0.12.1, the MCP campaign tools expose campaign read and write operations over the network using user-generated Bearer API tokens nxtc.... The application has an authorization model that restricts normal users to...
CVE-2026-12341
This vulnerability impacts all versions of IdentityIQ and allows an unauthenticated attacker unauthorized access to protected APIs and data due to improper validation of OAuth bearer tokens...
CVE-2026-12341 SailPoint IdentityIQ Improper Bearer Token Validation Vulnerability
This vulnerability impacts all versions of IdentityIQ and allows an unauthenticated attacker unauthorized access to protected APIs and data due to improper validation of OAuth bearer tokens...
EUVD-2026-46064
This vulnerability impacts all versions of IdentityIQ and allows an unauthenticated attacker unauthorized access to protected APIs and data due to improper validation of OAuth bearer tokens...
CVE-2026-12341
CVE-2026-12341 affects all versions of SailPoint IdentityIQ. The root cause is improper validation of OAuth bearer tokens, allowing an unauthenticated attacker to gain unauthorized access to protected APIs and data. Documented impact is high/critical (authentication bypass leading to exposure of ...
CVE-2026-12341
This vulnerability impacts all versions of IdentityIQ and allows an unauthenticated attacker unauthorized access to protected APIs and data due to improper validation of OAuth bearer tokens...
CVE-2026-46555
WhatsApp MCP Server is a Model Context Protocol MCP server for WhatsApp, enabling Claude to read and send WhatsApp messages. Prior to version 0.2.1, the whatsapp-bridge HTTP API listens on 127.0.0.1:8080 without authentication and without Host header validation, and the /api/send endpoint accepts...
CVE-2026-46555 WhatsApp MCP: Unauthenticated bridge API allows message sending and arbitrary file exfiltration
WhatsApp MCP Server is a Model Context Protocol MCP server for WhatsApp, enabling Claude to read and send WhatsApp messages. Prior to version 0.2.1, the whatsapp-bridge HTTP API listens on 127.0.0.1:8080 without authentication and without Host header validation, and the /api/send endpoint accepts...
CVE-2026-46555
The CVE applies to WhatsApp MCP Server, where the whatsapp-bridge HTTP API on 127.0.0.1:8080 is unauthenticated and lacks Host header validation. The /api/send endpoint accepts an absolute media_path, enabling a local caller (including sibling MCP servers, IDE extensions, or other processes in th...
CVE-2026-58482
In Network-AI, the ApprovalInbox HTTP surface (lib/approval-inbox.ts) exposes state-changing endpoints POST /approvals/:id/approve and /deny without authentication and with Access-Control-Allow-Origin: * across all routes. This allows any reachable actor to enumerate and approve high-risk actions...
CVE-2026-58482
Network-AI, a TypeScript/Node.js multi-agent orchestrator, has a shipped, exported, documented feature called ApprovalInbox lib/approval-inbox.ts. It is the network surface of the human-in-the-loop Approval Gate, which ApprovalGate uses to require explicit human approval for high-risk operations...
PT-2026-61653
Name of the Vulnerable Software and Affected Versions WhatsApp MCP Server versions prior to 0.2.1 Description The whatsapp-bridge HTTP API listens on 127.0.0.1:8080 without authentication or Host header validation. Additionally, the /api/send endpoint accepts an absolute media path parameter...
PT-2026-61736
Name of the Vulnerable Software and Affected Versions NextCRM version 0.12.1 Description The MCP campaign tools expose read and write operations over the network using user-generated Bearer API tokens nxtc .... The application fails to properly validate the authenticated user ID in multiple MCP...
CVE-2026-48022
@hapi/wreck is an HTTP client utility. Prior to 18.1.2, Wreck strips credential headers including Authorization, Cookie, and Proxy-Authorization before following a cross-origin redirect, but the origin check compares hostnames only and ignores scheme and port, so credentials are forwarded intact...
CVE-2026-48022 @hapi/wreck: Sensitive credential headers leak across cross-port and cross-scheme redirects
@hapi/wreck is an HTTP client utility. Prior to 18.1.2, Wreck strips credential headers including Authorization, Cookie, and Proxy-Authorization before following a cross-origin redirect, but the origin check compares hostnames only and ignores scheme and port, so credentials are forwarded intact...