32 vulnerabilities across 15 products scored HIGH or above on November 17, 2026.
- π΄ CRITICAL: 8
- π HIGH: 24
π΄ [CRITICAL] apache_software_foundation/apache_roller
1 CVE | CVSS 3.1: 9.8 | AAS 14.4
cpe:2.3:a:apache:apache_roller:*:*:*:*:*:*:*:*(>= 4.0.0, < 6.1.6)
Apache Roller versions 4.0.0 through 6.1.4 are affected by a critical remote code execution vulnerability (CVE-2026-129448, CVSS 9.8). The XML-RPC endpoint deserializes untrusted vendor extension types before authenticating the requester, allowing an unauthenticated remote attacker to execute arbitrary code on the server. This vulnerability is being actively exploited in the wild and is a broader restatement of CVE-2026-82384, which originally scoped impact to version 6.1.5 only.
Any organization running Apache Roller 4.0.0 through 6.1.5 should treat this as an emergency. Upgrade immediately to Apache Roller 6.1.6 or later, which disables the vulnerable extension type handling. If immediate patching is not possible, consider restricting or disabling the XML-RPC endpoint at the network or application layer until the upgrade can be applied. See the vendor advisory at lists.apache.org for further details.
- π΄ CVE-2026-129448 (CVSS 3.1: 9.8)
π΄ [CRITICAL] oracle_corporation/oracle_weblogic_server
7 CVEs | CVSS 3.1: 10.0 | AAS 13.3
cpe:2.3:a:oracle:oracle_weblogic_server:*:*:*:*:*:*:*:*(>= 12.2.1.4.0)cpe:2.3:a:oracle:oracle_weblogic_server:*:*:*:*:*:*:*:*(>= 14.1.1.0.0)cpe:2.3:a:oracle:oracle_weblogic_server:*:*:*:*:*:*:*:*(>= 14.1.2.0.0)cpe:2.3:a:oracle:oracle_weblogic_server:*:*:*:*:*:*:*:*(>= 15.1.1.0.0)cpe:2.3:a:oracle:oracle_weblogic_server:*:*:*:*:*:*:*:*(>= 15.1.1.0.0, < 15.1.1.0.0)
Oracle WebLogic Server versions 12.2.1.4.0, 14.1.1.0.0, 14.1.2.0.0, and 15.1.1.0.0 are affected by seven vulnerabilities, including at least one critical issue rated CVSS 10.0 in the TopLink Integration component that allows an unauthenticated remote attacker to fully compromise the server and potentially pivot to additional products via scope change. Multiple attack vectors across these CVEs target various WebLogic components, and several are described as easily exploitable over HTTP without any credentials or user interaction.
Organizations running Oracle WebLogic Server in any affected version should apply the patches from Oracle’s November 2026 Critical Patch Update immediately. Review the full advisory at oracle.com/security-alerts/cspunov2026.html for component-level detail and prioritize internet-facing WebLogic instances for emergency patching.
- π΄ CVE-2026-91569 (CVSS 3.1: 10.0)
- π΄ CVE-2026-91583 (CVSS 3.1: 9.8)
- π΄ CVE-2026-91570 (CVSS 3.1: 9.8)
- π΄ CVE-2026-91470 (CVSS 3.1: 9.8)
- π΄ CVE-2026-91456 (CVSS 3.1: 9.8)
- π΄ CVE-2026-91585 (CVSS 3.1: 9.8)
- π΄ CVE-2026-91469 (CVSS 3.1: 9.4)
π [HIGH] ontola/atomic-server
3 CVEs | CVSS 3.1: 9.8 | AAS 11.9
cpe:2.3:a:ontola:atomic-server:*:*:*:*:*:*:*:*(>= 0.29.0, < 0.40.3)cpe:2.3:a:ontola:atomic-server:*:*:*:*:*:*:*:*(>= 0.30.0, < 0.40.3)
Atomic Server versions 0.29.0 through 0.40.2 are affected by three vulnerabilities, including at least one critical issue rated CVSS 9.8 that allows an unauthenticated attacker to hijack the default setup invite and gain full write access to the entire Drive. The invite redemption logic fails to validate the redeemer identity, meaning an attacker-controlled public key can be used to create a privileged Agent on any fresh or unclaimed deployment without authentication. Public proof-of-concept details are available, making exploitation straightforward.
Anyone self-hosting Atomic Server should upgrade to version 0.40.3 or later immediately. If upgrading is not immediately possible, ensure that the default setup invite has already been claimed and that no unclaimed instances are exposed to the internet. See the vendor fix commit on GitHub for full technical details.
- π CVE-2026-69157 (CVSS 3.1: 9.8)
- π CVE-2026-69155 (CVSS 3.1: 8.7)
- π CVE-2026-69158 (CVSS 3.1: 8.6)
π [HIGH] oracle_corporation/oracle_access_manager
3 CVEs | CVSS 3.1: 10.0 | AAS 11.2
cpe:2.3:a:oracle:oracle_access_manager:*:*:*:*:*:*:*:*(>= 12.2.1.4.0)cpe:2.3:a:oracle:oracle_access_manager:*:*:*:*:*:*:*:*(>= 14.1.2.1.0)
Oracle Access Manager versions 12.2.1.4.0 and 14.1.2.1.0 are affected by three vulnerabilities, including at least one critical issue rated CVSS 10.0 in the Authentication Engine component that allows an unauthenticated remote attacker to fully compromise the product over HTTP with potential scope change impacting additional systems. Because Oracle Access Manager typically serves as a centralized authentication gateway, a compromise here could cascade across all applications and services relying on it for identity and access control.
Organizations running Oracle Access Manager on either affected version should apply the patches from Oracle’s November 2026 Critical Patch Update as an emergency priority. Review the full advisory at oracle.com/security-alerts/cspunov2026.html and assess whether any compensating controls such as network segmentation or WAF rules can reduce exposure while patching is underway.
- π CVE-2026-91500 (CVSS 3.1: 10.0)
- π CVE-2026-91510 (CVSS 3.1: 10.0)
- π CVE-2026-91507 (CVSS 3.1: 9.3)
π [HIGH] labredescefetrj/wegia
4 CVEs | CVSS 3.1: 9.8 | AAS 10.9
cpe:2.3:a:labredescefetrj:wegia:*:*:*:*:*:*:*:*(< 3.8.7)
WeGIA, a web management platform for charitable institutions, versions prior to 3.8.7 are affected by four vulnerabilities, including at least one critical issue rated CVSS 9.8 that allows an unauthenticated remote attacker to modify arbitrary member records by bypassing session validation entirely. Multiple endpoints lack proper authentication checks, enabling attackers to tamper with personal member data, corrupt records, and undermine data integrity without any credentials. Public exploit details are available, making these issues readily exploitable.
Organizations running WeGIA should upgrade to version 3.8.7 or later immediately. If patching cannot be done right away, restrict network access to the WeGIA application to trusted users only and audit member records for signs of unauthorized modification.
- π CVE-2026-61677 (CVSS 3.1: 9.8)
- π CVE-2026-61676 (CVSS 3.1: 9.8)
- π CVE-2026-61675 (CVSS 3.1: 9.8)
- π CVE-2026-61680 (CVSS 3.1: 9.8)
π [HIGH] pi-hole/ftl
2 CVEs | CVSS 4.0: 9.2 | AAS 10.8
cpe:2.3:a:pi-hole:ftl:*:*:*:*:*:*:*:*(>= 6.0, < 6.7)
Pi-hole FTL versions 6.0 through 6.7 are affected by two vulnerabilities, including at least one high-severity issue rated CVSS 9.2 that allows unauthenticated attackers to flood the WebUI login page and API endpoints without any rate or connection limits. Sustained request flooding can exhaust CPU resources, rendering the admin interface unresponsive and potentially degrading the underlying DNS blocking service that the broader network depends on.
Administrators running Pi-hole FTL in the affected version range should upgrade to version 6.8 or later, which addresses the missing rate-limiting controls. If immediate patching is not feasible, consider placing the Pi-hole WebUI behind a reverse proxy with rate limiting or restricting access to the admin interface to trusted management networks only.
- π CVE-2025-62165 (CVSS 4.0: 9.2)
- π CVE-2026-71304 (CVSS 3.1: 8.8)
π [HIGH] rucio/rucio
1 CVE | CVSS 3.1: 10.0 | AAS 10.8
cpe:2.3:a:rucio:rucio:*:*:*:*:*:*:*:*
Rucio versions 1.14.0 through 35.9.0, 38.0.0 through 38.6.0, 40.0.0 through 40.4.1, and 41.0.0 through 41.1.0 are affected by a critical authentication bypass vulnerability rated CVSS 10.0 that allows an unauthenticated attacker to impersonate any account. The SSH challenge token endpoint issues short-lived nonces that the authentication logic fails to distinguish from valid session tokens, meaning an attacker can request a challenge nonce for any arbitrary account and immediately reuse it as a full authentication token across all API endpoints.
Organizations using Rucio for scientific data management should upgrade immediately to version 35.9.1, 38.6.1, 40.4.2, or 41.1.1 depending on their release branch. Given the trivial exploitability and maximum severity rating, this should be treated as an emergency patch, and administrators should review access logs for any signs of unauthorized account activity using the SSH challenge token path.
- π CVE-2026-100397 (CVSS 3.1: 10.0)
π [HIGH] zoneminder/zoneminder
1 CVE | CVSS 3.1: 9.9 | AAS 10.2
cpe:2.3:a:zoneminder:zoneminder:*:*:*:*:*:*:*:*(< 1.38.4)
ZoneMinder versions prior to 1.38.4 are affected by a critical privilege escalation and remote code execution vulnerability rated CVSS 9.9 that allows any authenticated user, regardless of their permission level, to execute arbitrary commands on the server. The configuration editing endpoint fails to enforce authorization checks, enabling a low-privileged user to overwrite system path settings such as the FFmpeg binary path with attacker-controlled commands that are subsequently executed through built-in exec() calls during normal image and event processing.
Organizations running ZoneMinder should upgrade to version 1.38.4 or later immediately. Given that any authenticated user can exploit this to gain full server-level code execution, treat all ZoneMinder instances as high risk until patched, and audit system configurations for any unauthorized modifications to path-related settings.
- π CVE-2026-28273 (CVSS 3.1: 9.9)
π [HIGH] teableio/teable
1 CVE | CVSS 3.1: 8.8 | AAS 10.1
cpe:2.3:a:teableio:teable:*:*:*:*:*:*:*:*(< release.2026-07-21T11-27-40Z.2320)
Teable, an AI-powered spreadsheet platform, versions prior to the 2026-07-21 release are affected by a high-severity path traversal vulnerability rated CVSS 8.8 that allows any registered user to write arbitrary files to the server. The attachment upload endpoint accepts a client-controlled hash value as the storage filename without sanitizing path traversal sequences, enabling an authenticated attacker to place malicious files anywhere on the filesystem accessible to the application, which can lead to remote code execution. A public proof of concept is available.
Organizations self-hosting Teable with the default local storage provider should upgrade to release 2026-07-21T11-27-40Z.2320 or later immediately. If upgrading is not immediately feasible, consider switching to a non-local storage provider or restricting attachment upload access while the patch is applied.
- π CVE-2026-104100 (CVSS 3.1: 8.8)
π [HIGH] atlassian/confluence_data_center
1 CVE | CVSS 4.0: 8.7 | AAS 10.1
cpe:2.3:a:atlassian:confluence_data_center:*:*:*:*:*:*:*:*
Atlassian Confluence Data Center is affected by a high-severity path traversal vulnerability rated CVSS 8.7 that enables arbitrary file read and write operations, impacting a wide range of versions from 2.0.0 through current releases across the 6.x, 7.x, 8.x, and 9.x branches. This long-standing flaw means the vast majority of Confluence Data Center deployments are likely vulnerable, and exploitation details are available, making this a realistic attack vector for gaining access to sensitive data or achieving code execution on the server.
Organizations running Confluence Data Center should consult Atlassian’s security advisory immediately and apply the latest patched version for their release branch. Given the breadth of affected versions and the exploitability of this issue, prioritize internet-facing Confluence instances and review server file systems for any signs of unauthorized access or modification.
- π CVE-2026-21605 (CVSS 4.0: 8.7)
π [HIGH] gitlab/gitlab
2 CVEs | CVSS 3.1: 8.7 | AAS 10.0
cpe:2.3:a:gitlab:gitlab:*:*:*:*:*:*:*:*
GitLab CE/EE versions from 16.1 through 19.3.8, 19.4 through 19.4.7, and 19.5 through 19.5.5 are affected by two vulnerabilities, including at least one high-severity stored cross-site scripting issue rated CVSS 8.7 that allows an authenticated user to execute arbitrary JavaScript in the browsers of other users viewing Error Tracking pages. The improper sanitization of user input creates a risk of session hijacking, credential theft, and lateral movement within GitLab environments, particularly dangerous on instances with many users and sensitive repositories.
Organizations running self-managed GitLab should upgrade to versions 19.3.9, 19.4.8, or 19.5.6 depending on their release branch. Review the patch release notes at docs.gitlab.com for full details on both issues and prioritize patching on any internet-facing or widely shared GitLab instances.
- π CVE-2026-108153 (CVSS 3.1: 8.7)
- π CVE-2026-105739 (CVSS 3.1: 8.7)
π [HIGH] mndpsingh287/wp_file_manager
1 CVE | CVSS 4.0: 8.6 | AAS 10.0
cpe:2.3:a:mndpsingh287:wp_file_manager:*:*:*:*:*:*:*:*(< 8.0.7)
WP File Manager, a popular WordPress plugin, versions prior to 8.0.7 are affected by a high-severity file upload restriction bypass rated CVSS 8.6 that allows authenticated administrators to upload arbitrary PHP files and achieve remote code execution on the server. A misconfigured elFinder connector leaves the upload deny list empty, causing all file type checks to pass unconditionally, and attackers can also bypass filename restrictions by uploading under an allowed extension and renaming the file afterward. A public proof of concept is available.
WordPress site owners using WP File Manager should update to version 8.0.7 or later immediately. While exploitation requires administrator-level access, this is particularly dangerous in multi-user WordPress environments or where admin credentials have been compromised, as it provides a direct path to full server-level code execution.
- π CVE-2026-82025 (CVSS 4.0: 8.6)
π [HIGH] openssl/openssl
2 CVEs | CVSS 3.1: 7.7 | AAS 9.8
cpe:2.3:a:openssl:openssl:*:*:*:*:*:*:*:*
OpenSSL is affected by two vulnerabilities, including at least one high-severity denial-of-service issue rated CVSS 7.7 that allows a remote client to cause unbounded memory growth on QUIC servers. After completing a QUIC handshake, an attacker can repeatedly open and reset streams in a way that causes the server to retain stream state indefinitely, eventually exhausting all available memory and crashing every connection on the affected process.
Any organization running services that use OpenSSL’s QUIC server implementation should apply the latest OpenSSL security update released today. Review the advisory at openssl-library.org for version-specific fix details and prioritize patching on any internet-facing QUIC-enabled endpoints, as this vulnerability is exploitable by any client that can complete a TLS handshake.
- π CVE-2026-124709 (CVSS 3.1: 7.5)
- π CVE-2026-107493 (CVSS 3.1: 7.7)
π [HIGH] dataelement/bisheng
1 CVE | CVSS 4.0: 9.3 | AAS 9.7
cpe:2.3:a:dataelement:bisheng:*:*:*:*:*:*:*:*(< 3.0.0)
BISHENG versions prior to 3.0.0 are affected by a critical authentication bypass vulnerability rated CVSS 9.3 that allows an unauthenticated remote attacker to gain full administrative access by forging JWT tokens using a hard-coded default signing secret. An attacker can craft a valid HS256 token offline specifying the administrator user ID and role, then present it as a session cookie to gain unrestricted access to all users, workspaces, knowledge bases, and workflows without any credentials.
Organizations running BISHENG should upgrade to version 3.0.0 or later immediately and ensure the JWT signing secret has been changed from the default value. Any instance that has been exposed to untrusted networks while running an affected version should be investigated for unauthorized administrative activity, as exploitation is trivial and requires no prior access.
- π CVE-2026-130840 (CVSS 4.0: 9.3)
π [HIGH] thorsten/phpmyfaq
2 CVEs | CVSS 4.0: 9.2 | AAS 9.7
cpe:2.3:a:thorsten:phpmyfaq:*:*:*:*:*:*:*:*(>= 4.1.9, < 4.1.12)cpe:2.3:a:thorsten:phpmyfaq:*:*:*:*:*:*:*:*(>= 4.2.0-alpha, < 4.2.0-RC.2)
phpMyFAQ versions before 4.1.12 and 4.2.0-alpha versions before 4.2.0-RC.2 are affected by two vulnerabilities, including at least one critical authentication bypass rated CVSS 9.2 that allows an unauthenticated attacker to completely take over the application. The web installer fails to recognize legacy configuration files during 3.x upgrades, enabling an attacker to trigger a reinstallation against an attacker-controlled database and create a new administrator account with full privileges.
Organizations running phpMyFAQ should upgrade to version 4.1.12 or 4.2.0-RC.2 or later immediately. If immediate patching is not possible, restrict access to the web installer path and verify that existing configuration files are properly recognized by the application to prevent unauthorized reinstallation attempts.
- π CVE-2026-130371 (CVSS 4.0: 9.2)
- π CVE-2026-130369 (CVSS 4.0: 9.2)