Export limit exceeded: 428361 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Export limit exceeded: 428361 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Export limit exceeded: 428361 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Export limit exceeded: 428361 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Export limit exceeded: 428361 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Export limit exceeded: 428361 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Export limit exceeded: 428361 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Search
Search Results (428361 CVEs found)
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2026-109138 | 1 Nordic Semiconductor Asa | 1 Nrf Door Lock And Access Control Add-on | 2026-11-18 | N/A |
| In the Aliro access control reference applications of the Nordic Semiconductor nRF Door Lock and Access Control Add-on v1.0.0 through v1.1.1, built with Credential Issuer CA certificate-based issuer trust (CONFIG_DOOR_LOCK_CREDENTIAL_ISSUER_CA) and the Aliro Step-up phase (CONFIG_DOOR_LOCK_STEP_UP_PHASE) enabled, AccessManagerImpl::ProcessValidityIteration() treats a failed lookup of the Credential Issuer in the provisioned issuer array as success. For an issuer trusted through a certificate chain but not provisioned, the ValidityIteration (credential-rollback) check is therefore skipped. A former authorized holder with an old but correctly issuer-signed Access Document can be granted physical access after the issuer has advanced its iteration to revoke that credential. The default Matter provisioning configuration is not affected. Fixed in v1.2.0. | ||||
| CVE-2026-109148 | 1 Nordic Semiconductor Asa | 1 Nrf Door Lock And Access Control Add-on | 2026-11-18 | N/A |
| In the Aliro access control reference applications of the Nordic Semiconductor nRF Door Lock and Access Control Add-on v1.0.0 through v1.1.1, the stored Access Document record does not retain validFrom and validUntil. The cached public key path (VerifyPublicKey()) and the Kpersistent fast path (_VerifyKPersistentKey()) therefore never re-evaluate the Access Document validity period. An attacker who held a time-limited Aliro credential that was valid when first presented can continue to obtain physical access after the Access Document has expired, for as long as the cached record remains available. Fixed in v1.2.0. | ||||
| CVE-2026-109151 | 1 Nordic Semiconductor Asa | 1 Nrf Door Lock And Access Control Add-on | 2026-11-18 | N/A |
| In the Matter and Aliro Door Lock Application of the Nordic Semiconductor nRF Door Lock and Access Control Add-on v1.0.0 through v1.1.1 with CONFIG_DOOR_LOCK_STEP_UP_PHASE enabled, deleting a Credential Issuer passes the 1-based Matter credential index to ClearValidityIterations(), which expects a 0-based storage index. The intended issuer's ValidityIteration state is left in place, and the state of the adjacent, still-provisioned issuer is cleared. This resets that issuer's rollback protection. An attacker holding an older but correctly signed Access Document from the adjacent issuer, whose validity iteration had been superseded, can then potentially obtain physical access. Fixed in v1.2.0. | ||||
| CVE-2026-109154 | 1 Nordic Semiconductor Asa | 1 Nrf Door Lock And Access Control Add-on | 2026-11-18 | N/A |
| In the Matter door lock applications of the Nordic Semiconductor nRF Door Lock and Access Control Add-on v1.0.0 through v1.1.1, AccessManager::ValidateCredential() checks only credential occupancy and the secret bytes, and never reads the owning user's UserStatus. It also returns success when no owning user can be resolved. A user suspended by setting their status to OccupiedDisabled can continue to unlock the door with their previously assigned credential, and an orphaned but occupied credential is also accepted. Fixed in v1.2.0. | ||||
| CVE-2026-112209 | 1 Novanet | 2 Novanet's Website, Novanet S Website | 2026-11-18 | N/A |
| A Cross-Site Scripting (XSS) vulnerability reflected in the GET parameters `cod_primaria` and `cod_secundaria` of the Novanet Web endpoints `NNws_ShwNewDup` and `NPcd/NFG_VerNoticia`. User-provided data is reflected within a JavaScript block without proper sanitization or context-appropriate output encoding. An unauthenticated remote attacker could craft a manipulated URL that, when visited by a victim, would execute arbitrary JavaScript code in the victim’s browser, within the context of the affected site. The flaw resides in the platform’s shared code, so it could affect organizations using that vulnerable code. | ||||
| CVE-2026-118496 | 1 Codesys | 4 Automation Server Connector, Codesys Automation Server Connector, Codesys Service Tool and 1 more | 2026-11-18 | 7.5 High |
| The affected products process a server-supplied URL without sufficient validation. An unauthenticated remote attacker controlling a malicious Automation Server and tricking a user to trust it or performing a man-in-the-middle attack, can exploit this vulnerability by causing the affected product to process unintended content. Successful exploitation may result in arbitrary code execution with the privileges of the user running the affected product. | ||||
| CVE-2026-55172 | 2026-11-18 | N/A | ||
| Open OnDemand is an open-source high-performance computing portal. Prior to 4.1.6 and 4.2.3, apps/dashboard/config/initializers/session_store.rb stores dashboard sessions by default in a predictable /var/tmp/<username> directory, or in another location configured by an administrator, but omits PUN user directory ownership and mode 0700 validation. A local attacker can pre-create another user's directory, read the victim's session identifier and CSRF token after login, or stage a predetermined session identifier. ActiveSupport file-store deserialization of attacker-controlled cache data may also occur in the victim's context, enabling file modification or code execution with the victim's privileges. This issue is fixed in versions 4.1.6 and 4.2.3. | ||||
| CVE-2026-118497 | 1 Codesys | 4 Automation Server Connector, Codesys Automation Server Connector, Codesys Service Tool and 1 more | 2026-11-18 | 6.8 Medium |
| The affected products do not sufficiently validate CODESYS Automation Server TLS certificates when a user starts the certificate enrollment. An unauthenticated remote attacker performing a man-in-the-middle attack can exploit this vulnerability by supplying an untrusted certificate that is accepted as trusted. Successful exploitation may allow an attacker to intercept and manipulate communications between the CODESYS Automation Server and the PLC network. | ||||
| CVE-2026-118498 | 1 Codesys | 2 Automation Server Connector, Codesys Automation Server Connector | 2026-11-18 | 7.5 High |
| The CODESYS Automation Server Connector uses server-supplied file names without sufficient path traversal checks. An unauthenticated remote attacker controlling a malicious Automation Server and tricking a user to trust it, or performing a man-in-the-middle attack on a trusted communication channel, can exploit this vulnerability to write attacker-controlled files to arbitrary locations on the engineering workstation and subsequently achieve arbitrary code execution with user privileges. | ||||
| CVE-2026-129271 | 1 N-able | 1 N-central Patch Management Component | 2026-11-18 | N/A |
| The Patch Management Engine in N-central is vulnerable to LPE via attacker controlled metadata | ||||
| CVE-2026-127138 | 1 Pretix | 4 Pretixscan Android, Pretixscan Desktop, Pretixscan Ios and 1 more | 2026-11-18 | N/A |
| pretix provides a mechanism where ticket QR codes are cryptographically signed and can be verified by our pretixSCAN apps in offline mode without any database of valid tickets. pretixSCAN checks the signature to verify that the ticket was issued by the correct pretix event and compares the QR code against a list of revoked QR codes. A QR code becomes revoked when the order is canceled, or the ticket is changed in a way that a new QR code needs to be generated. However, the parsing of the QR code in all of our pretixSCAN apps contained a faulty computation, rendering the check for the correct length of the contents faulty. This way, an attacker is able to craft multiple QR codes for the same ticket which have the same content, but look different and therefore do not match against the revocation list. This does not allow to fabricate entirely new tickets, but it does allow to enter the event with e.g. a canceled ticket. This attack requires pretixSCAN to be scanning in offline mode and the "pretix signature scheme 1" to be used for the event's QR codes. If the attack is executed, the ticket unfortunately shows as valid (green) on the scanner but as invalid (red) on the server since the server later cannot match it to a ticket. We scanned the entire database of scans on pretix Hosted and could not find any traces of this being exploited in the past. | ||||
| CVE-2026-127139 | 1 Pretix | 1 Pretixscan Proxy | 2026-11-18 | N/A |
| pretixSCAN Proxy does not use a secure random generator to generate initialization tokens and API keys for the connection between pretixSCAN devices and the pretixSCAN Proxy. This could allow a skilled attacker with access to at least some of the tokens to predict the value of other tokens more easily. pretixSCAN is usually used on local networks and the level of exposure heavily depends on the structure of that network. If you want to be extra careful, it might make sense to reconnect your devices to the proxy after the update. | ||||
| CVE-2026-127140 | 2 Pretix, Wordpress-extensions | 2 Pretix Widget Wordpress Plugin, Pretiz Widget | 2026-11-18 | N/A |
| Our WordPress plugin for the pretix Widget performs HTTP calls to pre-fetch CSS and JS files into a local cache and stores them publicly on the WordPress instance. These HTTP calls are made with wp_remote_get, not wp_safe_remote_get, and therefore allow SSRF with body extraction. Exploiting this requires sufficient WordPress permissions to create or modify pages. | ||||
| CVE-2026-12239 | 2 Kevonadonis, Wordpress-extensions | 2 Wp Abstracts, Wp Abstracts | 2026-11-18 | 8.8 High |
| The WP Abstracts plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 2.7.6. This is due to a missing capability check on the wpabs_save_regform AJAX action and the use of a static, frontend-exposed nonce that allows any authenticated user to persist attacker-controlled form schemas with arbitrary wpSync mappings that are later used as user meta keys in the wpabstracts_sync_wpfields function. This makes it possible for authenticated attackers, with subscriber-level access and above, to elevate their privileges to administrator. | ||||
| CVE-2026-130594 | 1 Scalar | 1 Scalar-ninja | 2026-11-18 | 5.4 Medium |
| Scalar scalar-ninja 0.1.0 before 0.3.3 contains a cross-site scripting vulnerability that allows attackers to inject scripts by supplying unescaped ScalarConfig title values. Attackers controlling title metadata can close the title element with </title> and inject a script tag that executes in the documentation origin for API reference visitors. | ||||
| CVE-2026-130593 | 1 Scalar | 1 Scalar-ninja | 2026-11-18 | 5.4 Medium |
| Scalar scalar-ninja 0.1.0 before 0.3.3 contains a cross-site scripting vulnerability in get_scalar_api_reference() that embeds unescaped OpenAPI content inside an inline script element. Attackers can supply an OpenAPI document containing a </script><script> sequence in content or sources to execute scripts in the documentation origin for every user viewing the API reference. | ||||
| CVE-2026-130590 | 1 React-native-webview | 1 React-native-webview | 2026-11-18 | 4.3 Medium |
| react-native-webview 11.25.1 through 17.1.0 on Android contains a denial of service vulnerability that allows web content to crash the host application via malformed Content-Disposition headers. Attackers can serve a download whose filename* parameter has invalid percent-encoding, triggering an uncaught IllegalArgumentException in URLUtil.parseContentDisposition on the main thread to terminate the app. | ||||
| CVE-2026-130589 | 1 Emitter-io | 1 Emitter | 2026-11-18 | 8.1 High |
| Emitter through 3.1 contains a privilege escalation vulnerability that allows any channel key holder to forge a master key because channel keys use bare XOR Salsa20 encryption without a MAC or signature. Attackers can flip the permissions byte to the master value and present the forged key to the keygen service to mint keys with arbitrary permissions on every channel of the contract. | ||||
| CVE-2026-130588 | 1 Openfunction | 1 Openfunction | 2026-11-18 | 6.5 Medium |
| OpenFunction through 1.2.0 contains a NULL pointer dereference vulnerability in getServingRun that allows users permitted to create Serving resources to crash the operator by omitting the triggers section. Attackers can submit a Serving with nil Spec.Triggers to crash-loop the controller-manager, halting Function and Serving reconciliation cluster-wide until the object is deleted. | ||||
| CVE-2026-130587 | 1 Openfunction | 1 Openfunction | 2026-11-18 | 9.9 Critical |
| OpenFunction through 1.2.0 contains a privilege escalation vulnerability that allows namespace tenants to create privileged host-access pods by supplying unrestricted PodSpec templates in Function and Serving resources. Attackers with only Function or Serving create permissions can set privileged, hostNetwork, hostPID, or hostPath fields to mount the worker node's root filesystem and escalate to node access. | ||||