Critical security advisoryCriticalFlagged by our vulnerability database: PHP2Shell is on CISA’s exploited list. Most WordPress hosting runs PHP. See if your site is affectedFlagged by our vulnerability database: PHP2Shell is being exploited. DetailsExploited: PHP2Shell. Check your site
HuttenlocherTechnologies
Updated 3 h ago

Vulnerability database

Every flaw the U.S. government’s cybersecurity agency (CISA) has confirmed attackers are using, plus the new WordPress plugin and theme bugs published each day, sorted by what they mean for a small business. We refresh it twice a day. If you see something your website or office runs, tell us.

1,764exploited flaws on CISA’s list
35added in the last 30 days
472new WordPress flaws this week
390,714entries in the database

3,789 results · page 4 of 76

  • Oct 5, 2026Insufficient boundary validation in the USB boot mode implementation of AMD Zynq™ UltraScale+ MPSoC and RFSoC devices could allow unbounded Device Firmware UpgrCVE-2026-0461 · Other software · AMD · reported by psirt@amd.comHigh 7.5

    Insufficient boundary validation in the USB boot mode implementation of AMD Zynq™ UltraScale+ MPSoC and RFSoC devices could allow unbounded Device Firmware Upgrade (DFU) download requests to overflow the DDR receive buffer into FSBL memory, potentially resulting in unauthorized code execution during the boot process. This issue could impact the confidentiality, integrity, or availability of affected system.

    Product
    Zynq™ UltraScale+ MPSoCs
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Oct 5, 2026Papermerge 3.5.3 allows remote code execution by a standard user via directory traversal in a /api/documents/upload call.CVE-2026-105314 · Other software · Papermerge · reported by MITREHigh 7.5

    Papermerge 3.5.3 allows remote code execution by a standard user via directory traversal in a /api/documents/upload call. A Python .pth file can be written to site-packages, and its code is executed upon the next start of the Python interpreter.

    Product
    Papermerge
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Oct 3, 2026Nelio Content – Editorial Calendar & Social Media Auto-Posting: Authorization bypassCVE-2026-94505 · WordPress plugins & themes · reported by WordfenceHigh 8.1

    The Nelio Content – Editorial Calendar & Social Media Auto-Posting plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 4.5.0 This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with contributor-level access and above, to permanently delete any reusable social message (nc_reusable_social post), including those authored by administrators or other privileged users.

    Product
    Nelio Content – Editorial Calendar & Social Media Auto-Posting
    Affected
    up to 4.5.0
    What to do
    Affects up to 4.5.0. Update Nelio Content – Editorial Calendar & Social Media Auto-Posting to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Oct 3, 2026VikAppointments Services Booking Calendar: Arbitrary file deletionCVE-2026-87115 · WordPress plugins & themes · reported by WordfenceCritical 9.1

    The VikAppointments Services Booking Calendar plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the extract function in all versions up to, and including, 1.2.21. This makes it possible for unauthenticated attackers to delete arbitrary files on the server, which can easily lead to remote code execution when the right file is deleted (such as wp-config.php). Exploitation requires at least one File-type custom field to be published on the confirmation page shortcode, as this field is not created by default during plugin installation.

    Product
    VikAppointments Services Booking Calendar
    Affected
    up to 1.2.21
    What to do
    Affects up to 1.2.21. Update VikAppointments Services Booking Calendar to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Oct 2, 2026oRPC is a tool that helps build APIs that are end-to-end type-safe and adhere to OpenAPI standards.CVE-2026-103918 · Other software · middleapi · reported by GitHubMedium 6.5

    oRPC is a tool that helps build APIs that are end-to-end type-safe and adhere to OpenAPI standards. Prior to 1.14.10, the @orpc/zod ZodSmartCoercionPlugin and experimental_ZodSmartCoercionPlugin collect object and record properties in plain objects and resolve shape keys through the prototype chain. A remote client that can reach a procedure with an object or record input can supply __proto__ to replace the prototype of the returned request object, allowing attacker-controlled inherited values to reach application lookups. For object schemas, keys such as constructor, toString, and __proto__ can instead resolve inherited members as Zod schemas and cause an unhandled TypeError before validation. The global Object.prototype, unrelated objects, other requests, and other users are not modified, and the availability effect is limited to crafted requests rather than persistent process-wide state. This issue is fixed in version 1.14.10.

    Product
    orpc
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Oct 2, 2026oRPC is a tool that helps build APIs that are end-to-end type-safe and adhere to OpenAPI standards.CVE-2026-103036 · Other software · middleapi · reported by GitHubMedium 6.5

    oRPC is a tool that helps build APIs that are end-to-end type-safe and adhere to OpenAPI standards. Prior to 1.14.9, the @orpc/json-schema SmartCoercionPlugin uses JsonSchemaCoercer to collect object properties in a plain object and to resolve schema.properties entries through the prototype chain. A remote client that can reach a procedure with an object input schema can supply __proto__ to replace the prototype of the single coerced request object, or supply Object.prototype member names such as constructor and toString so inherited values are treated as sub-schemas and pass the coercer's satisfaction check. Attacker-controlled inherited properties can consequently affect handler, Object.assign, or configuration lookups, while legitimate __proto__ properties are dropped. The global Object.prototype, unrelated objects, other requests, and other users are not modified, and downstream schema validation still runs. This issue is fixed in version 1.14.9.

    Product
    orpc
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Oct 2, 2026Booking Calendar: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')CVE-2026-39601 · WordPress plugins & themes · reported by PatchstackLow 3.7

    Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') vulnerability in WPdevelop Booking Calendar booking allows Leveraging Race Conditions.This issue affects Booking Calendar: from n/a through 11.8.4.

    Product
    Booking Calendar
    Affected
    up to 11.8.4
    What to do
    Affects up to 11.8.4. Update Booking Calendar to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Oct 2, 2026Allocation of resources without limits or throttling vulnerability in Apache Thrift dart bindings.CVE-2026-94648 · Websites & servers · Apache Software Foundation · reported by security@apache.orgHigh 8.2

    Allocation of resources without limits or throttling vulnerability in Apache Thrift dart bindings. This issue affects Apache Thrift: before 0.25.0. Users are recommended to upgrade to version 0.25.0, which fixes the issue.

    Product
    Apache Thrift
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Oct 2, 2026Memory allocation with excessive size value, Improper handling of length parameter inconsistency vulnerability in Apache Thrift Dart bindings.CVE-2026-94633 · Websites & servers · Apache Software Foundation · reported by security@apache.orgHigh 8.7

    Memory allocation with excessive size value, Improper handling of length parameter inconsistency vulnerability in Apache Thrift Dart bindings. This issue affects Apache Thrift: before 0.25.0. Users are recommended to upgrade to version 0.25.0, which fixes the issue.

    Product
    Apache Thrift
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Oct 2, 2026Uncontrolled Recursion vulnerability in Apache Thrift Dart and Java ME bindings.CVE-2026-85493 · Websites & servers · Apache Software Foundation · reported by security@apache.orgHigh 8.7

    Uncontrolled Recursion vulnerability in Apache Thrift Dart and Java ME bindings. This issue affects Apache Thrift: before 0.25.0. Users are recommended to upgrade to version 0.25.0, which fixes the issue.

    Product
    Apache Thrift
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Oct 2, 2026Appointment Booking Plugin – LatePoint | Calendar & Scheduling for: Insecure Direct Object ReferenceCVE-2026-94432 · WordPress plugins & themes · reported by WordfenceMedium 5.3

    The Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress plugin for WordPress is vulnerable to Insecure Direct Object Reference in versions up to, and including, 5.7.1 via the OsPaypalConnectController::create_order_for_transaction() action registered as a public (unauthenticated) route through wp_ajax_nopriv_latepoint_route_call. The handler loads an OsInvoiceModel by a sequential integer 'invoice_id' with no access-key/UUID or ownership check (the sibling Stripe and Razorpay handlers require a 128-bit access-key UUID via OsInvoicesHelper::get_invoice_by_key), and then calls OsTransactionIntentHelper::create_or_update_transaction_intent() which persists a transaction intent tied to the target invoice's customer_id, order_id and charge_amount and regenerates its intent_key before the PayPal-configured guard is reached. This makes it possible for unauthenticated attackers to enumerate invoices belonging to arbitrary customers, create unauthorized transaction-intent rows linked to another customer's data, and overwrite the intent_key of any in-flight NEW-status transaction intent — invalidating the intent_key that legitimate Stripe/Razorpay flows are waiting o

    Product
    Appointment Booking Plugin – LatePoint | Calendar & Scheduling for
    Affected
    up to 5.7.1
    What to do
    Affects up to 5.7.1. Update Appointment Booking Plugin – LatePoint | Calendar & Scheduling for to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Oct 2, 2026Events Calendar: Does not validate or sanitise data submitted to an unauthenticated AJAX action before merging it into its rendering contextCVE-2026-84740 · WordPress plugins & themes · reported by WPScanMedium 6.5

    The Events Calendar WordPress plugin before 6.17.5.1 does not validate or sanitise data submitted to an unauthenticated AJAX action before merging it into its rendering context, allowing unauthenticated users to execute arbitrary shortcodes registered on the site.

    Product
    Events Calendar
    Fixed in
    6.17.5.1
    What to do
    Update Events Calendar to 6.17.5.1 or newer.
  • Oct 1, 2026Appointment Hour Booking – Booking Calendar: Stored DOM-Based Cross-Site ScriptingCVE-2026-96573 · WordPress plugins & themes · reported by WordfenceHigh 7.2

    The Appointment Hour Booking – Booking Calendar plugin for WordPress is vulnerable to Stored DOM-Based Cross-Site Scripting via Booking Form Single-Line Field via Schedule Calendar List Renderer in all versions up to, and including, 1.5.97 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Exploitation requires the 'list_readmore_numberofwords' Other Parameters setting to be configured with a positive integer value; the default value of 0 bypasses the decode-and-truncate branch entirely and is not exploitable through this sink.

    Product
    Appointment Hour Booking – Booking Calendar
    Affected
    up to 1.5.97
    What to do
    Affects up to 1.5.97. Update Appointment Hour Booking – Booking Calendar to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Oct 1, 2026The Appointment Booking Plugin – LatePoint | Calendar & Scheduling for: Arbitrary shortcode executionCVE-2026-92966 · WordPress plugins & themes · reported by WordfenceCritical 9.1

    The The Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress plugin for WordPress is vulnerable to arbitrary shortcode execution in all versions up to, and including, 5.7.0. This is due to the software allowing users to execute an action that does not properly validate a value before running do_shortcode. This makes it possible for unauthenticated attackers to execute arbitrary shortcodes. The payload is planted during the unauthenticated booking flow and triggered when the Customer Cabinet block rendered by render_customer_dashboard() outputs the stored name into the content stream, where WordPress core's do_shortcode filter at priority 11 re-parses and executes it.

    Product
    The Appointment Booking Plugin – LatePoint | Calendar & Scheduling for
    Affected
    up to 5.7.0
    What to do
    Affects up to 5.7.0. Update The Appointment Booking Plugin – LatePoint | Calendar & Scheduling for to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Sep 30, 2026PyJWT is a Python implementation of JSON Web Token standards.CVE-2026-103001 · Other software · jpadilla · reported by GitHubMedium 6.5

    PyJWT is a Python implementation of JSON Web Token standards. From 2.11.0 through 2.13.0, PyJWT's PyJWT._merge_options() method can modify a caller-supplied mutable options mapping when verify_signature is false. If an application reuses that same mapping for a later decode() or decode_complete() call and changes verify_signature to true, the mapping can retain false values for expiration, not-before, issued-at, audience, issuer, subject, and JWT ID checks. A signed token with invalid registered claims can then be accepted without disabling signature verification, but applications that create a fresh options mapping for each call are not affected.

    Product
    pyjwt
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Sep 30, 2026In camel-ai camel 0.2.91a1, v0.2.91a2 and v0.2.91a3, TerminalToolkit.shell_exec allows prompt-driven shell command execution without an approval boundary.CVE-2026-51858 · Other software · reported by MITRECritical 9.8

    In camel-ai camel 0.2.91a1, v0.2.91a2 and v0.2.91a3, TerminalToolkit.shell_exec allows prompt-driven shell command execution without an approval boundary.

    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Sep 30, 2026Contributor Broken Access Control in The Events Calendar <= 6.17.5 versions.CVE-2026-97285 · WordPress plugins & themes · reported by PatchstackMedium 5.4

    Contributor Broken Access Control in The Events Calendar <= 6.17.5 versions.

    Affected
    up to 6.17.5
    What to do
    Affects up to 6.17.5. Update the plugin to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Sep 30, 2026A trust-boundary flaw in CRI-O's sandbox state persistence allows attacker-influenced pod metadata to overwrite CRI-O's own reserved sandbox bookkeeping; once rCVE-2026-62146 · Other software · Red Hat · reported by Red HatHigh 7.8

    A trust-boundary flaw in CRI-O's sandbox state persistence allows attacker-influenced pod metadata to overwrite CRI-O's own reserved sandbox bookkeeping; once reloaded as trusted after a restart, a later container recreate in that sandbox can expose a host-side runtime-management resource inside the container, enabling container escape.

    Product
    Red Hat OpenShift Container Platform 4.16
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Sep 29, 2026Sandbox escape due to incorrect boundary conditions in the XPCOM component.CVE-2026-100819 · Computers, phones & browsers · Mozilla · reported by security@mozilla.orgCritical 9.6

    Sandbox escape due to incorrect boundary conditions in the XPCOM component. This vulnerability was fixed in Firefox ESR 153.4, Thunderbird 157, Thunderbird 140.17, Thunderbird 153.4, Firefox 157, Firefox ESR 115.42, and Firefox ESR 140.17.

    Product
    Firefox
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Sep 29, 2026Incorrect boundary conditions in the JavaScript Engine: JIT component.CVE-2026-100814 · Computers, phones & browsers · Mozilla · reported by security@mozilla.orgHigh 8.8

    Incorrect boundary conditions in the JavaScript Engine: JIT component. This vulnerability was fixed in Firefox ESR 153.4, Thunderbird 157, Thunderbird 153.4, and Firefox 157.

    Product
    Firefox
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Sep 29, 2026Sandbox escape due to incorrect boundary conditions in the Internationalization component.CVE-2026-100794 · Computers, phones & browsers · Mozilla · reported by security@mozilla.orgCritical 9.6

    Sandbox escape due to incorrect boundary conditions in the Internationalization component. This vulnerability was fixed in Firefox ESR 153.4, Thunderbird 157, Thunderbird 140.17, Thunderbird 153.4, Firefox 157, and Firefox ESR 140.17.

    Product
    Thunderbird
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Sep 29, 2026Privilege escalation due to incorrect boundary conditions in the Graphics component.CVE-2026-100782 · Computers, phones & browsers · Mozilla · reported by security@mozilla.orgHigh 8.8

    Privilege escalation due to incorrect boundary conditions in the Graphics component. This vulnerability was fixed in Firefox ESR 153.4, Thunderbird 157, Thunderbird 140.17, Thunderbird 153.4, Firefox 157, Firefox ESR 115.42, and Firefox ESR 140.17.

    Product
    Firefox
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Sep 29, 2026Sandbox escape due to incorrect boundary conditions in the Graphics: WebRender component.CVE-2026-100781 · Computers, phones & browsers · Mozilla · reported by security@mozilla.orgCritical 9.6

    Sandbox escape due to incorrect boundary conditions in the Graphics: WebRender component. This vulnerability was fixed in Firefox ESR 153.4, Thunderbird 157, Thunderbird 140.17, Thunderbird 153.4, Firefox 157, Firefox ESR 115.42, and Firefox ESR 140.17.

    Product
    Firefox
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Sep 29, 2026Privilege escalation due to incorrect boundary conditions in the Graphics: WebGPU component.CVE-2026-100764 · Computers, phones & browsers · Mozilla · reported by security@mozilla.orgHigh 8.8

    Privilege escalation due to incorrect boundary conditions in the Graphics: WebGPU component. This vulnerability was fixed in Thunderbird 157 and Firefox 157.

    Product
    Thunderbird
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Sep 29, 2026Incorrect boundary conditions in the Graphics: WebGPU component.CVE-2026-100763 · Computers, phones & browsers · Mozilla · reported by security@mozilla.orgCritical 9.1

    Incorrect boundary conditions in the Graphics: WebGPU component. This vulnerability was fixed in Thunderbird 157 and Firefox 157.

    Product
    Thunderbird
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Sep 29, 2026Incorrect boundary conditions in the Audio/Video: Playback component.CVE-2026-100756 · Computers, phones & browsers · Mozilla · reported by security@mozilla.orgHigh 8.1

    Incorrect boundary conditions in the Audio/Video: Playback component. This vulnerability was fixed in Firefox ESR 153.4, Thunderbird 157, Thunderbird 140.17, Thunderbird 153.4, Firefox 157, Firefox ESR 115.42, and Firefox ESR 140.17.

    Product
    Firefox
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Sep 28, 2026PyJWT is a Python implementation of JSON Web Token standards.CVE-2026-102275 · Other software · jpadilla · reported by GitHubMedium 6.5

    PyJWT is a Python implementation of JSON Web Token standards. From 2.1.0 until 2.15.0, PyJWT OKPAlgorithm.from_jwk in jwt/algorithms.py is affected because private-JWK import path does not compare the public key derived from d with x. This occurs when an OKP private JWK supplies non-corresponding x and d components. As a result, identity derived from x can differ from operations performed with d. Consequently, if an integration also accepts private key parameters from a proof header without rejecting them, an attacker may use a stolen sender-constrained token without the legitimate private key. This issue is fixed in version 2.15.0.

    Product
    pyjwt
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Sep 28, 2026PyJWT is a Python implementation of JSON Web Token standards.CVE-2026-102274 · Other software · jpadilla · reported by GitHubMedium 5.9

    PyJWT is a Python implementation of JSON Web Token standards. From 2.9.0 until 2.14.0, PyJWKSet does not catch the plain ValueError raised for malformed RSA JWK components by RSAAlgorithm.from_jwk in jwt/api_jwk.py. This occurs when a JWK Set contains a malformed RSA key alongside otherwise usable keys. As a result, one malformed member aborts construction of the entire PyJWKSet. Consequently, applications can experience authentication failures or request-level denial of service. This issue is fixed in version 2.14.0.

    Product
    pyjwt
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Sep 28, 2026PyJWT is a Python implementation of JSON Web Token standards.CVE-2026-102273 · Other software · jpadilla · reported by GitHubHigh 7.4

    PyJWT is a Python implementation of JSON Web Token standards. From 2.13.0 until 2.14.0, PyJWT HMACAlgorithm.prepare_key is affected because HMAC key guard only recognizes top-level public JWK forms and misses container representations. This occurs when an application allows HMAC and asymmetric algorithms and passes a public JWK container as the raw key. As a result, public asymmetric key material is accepted as the HMAC secret. Consequently, an attacker who knows the public key can forge a token with arbitrary authenticated claims. This issue is fixed in version 2.14.0.

    Product
    pyjwt
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Sep 28, 2026PyJWT is a Python implementation of JSON Web Token standards.CVE-2026-102272 · Other software · jpadilla · reported by GitHubHigh 7.4

    PyJWT is a Python implementation of JSON Web Token standards. From 2.13.0 until 2.14.0, HMACAlgorithm.prepare_key in jwt/algorithms.py is affected because raw-JWK detector does not normalize accepted Unicode byte-order marks before checking for JSON. This occurs when a public JWK is prefixed with a UTF-8 BOM and used in a mixed-algorithm verification path. As a result, public JWK bypasses asymmetric-key detection and becomes the HMAC secret. Consequently, an attacker who knows the public key can forge authenticated tokens. This issue is fixed in version 2.14.0.

    Product
    pyjwt
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Sep 28, 2026PyJWT is a Python implementation of JSON Web Token standards.CVE-2026-102271 · Other software · jpadilla · reported by GitHubHigh 7.4

    PyJWT is a Python implementation of JSON Web Token standards. From 2.4.0 until 2.14.0, PyJWT HMACAlgorithm.prepare_key is affected because asymmetric-key guard relies on textual markers that are absent from DER encoding. This occurs when an application mixes HMAC and asymmetric algorithms and supplies a DER public key as the shared verification key. As a result, PyJWT uses public DER bytes as an HMAC secret. Consequently, an attacker who knows the public key can forge authenticated HMAC tokens. This issue is fixed in version 2.14.0.

    Product
    pyjwt
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Sep 28, 2026PyJWT is a Python implementation of JSON Web Token standards.CVE-2026-102270 · Other software · jpadilla · reported by GitHubMedium 4.4

    PyJWT is a Python implementation of JSON Web Token standards. Prior to 2.14.0, PyJWT is_pem_format is affected because lazy PEM regular expression backtracks extensively. This occurs when a certificate-like input contains repeated BEGIN markers without a matching END marker. As a result, is_pem_format performs unbounded backtracking while searching for a PEM end marker. Consequently, an attacker can cause intensive CPU consumption. This issue is fixed in version 2.14.0.

    Product
    pyjwt
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Sep 28, 2026PyJWT is a Python implementation of JSON Web Token standards.CVE-2026-102269 · Other software · jpadilla · reported by GitHubMedium 4.8

    PyJWT is a Python implementation of JSON Web Token standards. Prior to 2.14.0, PyJWT signature segment is affected because signature segment decoding accepts characters outside the canonical Base64URL representation. This occurs when non-Base64URL characters are appended to a valid compact JWS signature segment. As a result, base64url_decode produces the same signature bytes for different serialized segments. Consequently, raw-token revocation checks can fail to recognize an equivalent modified token. This issue is fixed in version 2.14.0.

    Product
    pyjwt
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Sep 28, 2026PyJWT is a Python implementation of JSON Web Token standards.CVE-2026-102268 · Other software · jpadilla · reported by GitHubCritical 9.1

    PyJWT is a Python implementation of JSON Web Token standards. Prior to 2.14.0, is_pem_format in jwt/utils.py is affected because is_pem_format does not recognize every PEM representation accepted by the cryptography loader. This occurs when an application mixes HMAC and asymmetric algorithms and supplies a mutated public-key PEM as raw key bytes. As a result, HMACAlgorithm.prepare_key treats the unrecognized asymmetric public key as an HMAC secret. Consequently, an attacker who knows the public key can forge authenticated HMAC tokens. This issue is fixed in version 2.14.0.

    Product
    pyjwt
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Sep 28, 2026PyJWT is a Python implementation of JSON Web Token standards.CVE-2026-102267 · Other software · jpadilla · reported by GitHubHigh 7.4

    PyJWT is a Python implementation of JSON Web Token standards. Prior to 2.14.0, PyJWT PyJWKClient is affected because redirect destinations are not revalidated against the JWKS trust boundary. This occurs when a configured trusted JWKS endpoint returns an attacker-influenced redirect. As a result, PyJWKClient follows the redirect and consumes the redirected response as key material. Consequently, forwarded credentials may be disclosed or verification keys may be substituted. This issue is fixed in version 2.14.0.

    Product
    pyjwt
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Sep 28, 2026PyJWT is a Python implementation of JSON Web Token standards.CVE-2026-102266 · Other software · jpadilla · reported by GitHubHigh 7.4

    PyJWT is a Python implementation of JSON Web Token standards. From 2.13.0 until 2.14.0, HMACAlgorithm.from_jwk is affected because PyJWK verification path used the decoded key without applying prepare_key validation. This occurs when a trusted JWK Set contains an oct entry with an empty k value. As a result, an attacker signs an HMAC token with the same zero-length key accepted by PyJWT. Consequently, forged token can carry arbitrary authenticated claims. This issue is fixed in version 2.14.0.

    Product
    pyjwt
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Sep 28, 2026PyJWT is a Python implementation of JSON Web Token standards.CVE-2026-102265 · Other software · jpadilla · reported by GitHubMedium 5.3

    PyJWT is a Python implementation of JSON Web Token standards. From 2.13.0 until 2.14.0, PyJWS._load in jwt/api_jws.py is affected because parser catches ValueError but not RecursionError. This occurs when a deeply nested token header reaches json.loads. As a result, RecursionError escapes the documented PyJWT error hierarchy. Consequently, an unauthenticated malformed token can cause a request-level failure and HTTP 500. This issue is fixed in version 2.14.0.

    Product
    pyjwt
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Sep 28, 2026PyJWT is a Python implementation of JSON Web Token standards.CVE-2026-101918 · Other software · jpadilla · reported by GitHubMedium 5.3

    PyJWT is a Python implementation of JSON Web Token standards. From 2.0.0a1 until 2.15.0, PyJWT PyJWKClient.get_signing_key_from_jwt is affected because payload parser catches ValueError but not RecursionError. This occurs when an attacker-controlled recursively nested payload reaches json.loads. As a result, documented PyJWT exception handling does not contain the failure. Consequently, an unauthenticated request can raise an exception that may produce an HTTP 500 response. The advisory-defined affected implementation also includes jwt/api_jwt.py, verify_signature=False. This issue is fixed in version 2.15.0.

    Product
    pyjwt
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Sep 28, 2026PyJWT is a Python implementation of JSON Web Token standards.CVE-2026-101917 · Other software · jpadilla · reported by GitHubMedium 5.3

    PyJWT is a Python implementation of JSON Web Token standards. Prior to 2.14.0, PyJWT get_signing_key_from_jwt is affected because unknown kid misses force refreshes without a negative cache or minimum refresh interval. This occurs when unauthenticated tokens repeatedly use the same unknown kid or varying kid values absent from the cached JWKS. As a result, each cache miss causes PyJWKClient to refresh the JWKS. Consequently, attacker traffic can amplify outbound requests to the configured JWKS endpoint. This issue is fixed in version 2.14.0.

    Product
    pyjwt
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Sep 25, 2026An unauthenticated calendar sender can place active markup in a COUNTER message's RFC From address.CVE-2026-93647 · Email & office · Zimbra · reported by cve@rapid7.comCritical 9.3

    An unauthenticated calendar sender can place active markup in a COUNTER message's RFC From address. Selecting the message in Zimbra Classic triggers stored XSS, allowing the attacker to access mailbox data and act as the victim.

    Product
    Zimbra Collaboration Suite (ZCS)
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Sep 24, 2026In the Linux kernel, the following vulnerability has been resolved: ACPICA: add boundary checks in acpi_ps_get_next_field() Add boundary checks in acpi_ps_getCVE-2026-97454 · Computers, phones & browsers · Linux · reported by 416baaa9-dc9f-4396-8d5f-8c081fb06d67High 7.7

    In the Linux kernel, the following vulnerability has been resolved: ACPICA: add boundary checks in acpi_ps_get_next_field() Add boundary checks in acpi_ps_get_next_field() to prevent out-of-bounds access.

    Product
    Linux
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Sep 24, 2026In the Linux kernel, the following vulnerability has been resolved: ACPICA: add boundary checks in two places Add boundary checks in acpi_ps_get_next_namestriCVE-2026-97444 · Computers, phones & browsers · Linux · reported by 416baaa9-dc9f-4396-8d5f-8c081fb06d67High 7.7

    In the Linux kernel, the following vulnerability has been resolved: ACPICA: add boundary checks in two places Add boundary checks in acpi_ps_get_next_namestring() and acpi_ps_peek_opcode() to prevent out-of-bounds access.

    Product
    Linux
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Sep 24, 2026In the Linux kernel, the following vulnerability has been resolved: RDMA/umem: Be careful about boundary conditions in ib_umem_find_best_pgsz() Several cornerCVE-2026-97421 · Computers, phones & browsers · Linux · reported by 416baaa9-dc9f-4396-8d5f-8c081fb06d67High 7.8

    In the Linux kernel, the following vulnerability has been resolved: RDMA/umem: Be careful about boundary conditions in ib_umem_find_best_pgsz() Several corner cases, especially important on 32 bits: - umem->iova is u64, the function argument should pass in u64 or iova will be truncated - Check that the length is not too large for the iova - Check that lengths > 4G don't overflow the GENMASK

    Product
    Linux
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Sep 24, 2026In the Linux kernel, the following vulnerability has been resolved: wifi: iwlwifi: mvm: fix an off-by-1 boundary check Before looking at the 11th byte, check CVE-2026-93797 · Computers, phones & browsers · Linux · reported by 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    In the Linux kernel, the following vulnerability has been resolved: wifi: iwlwifi: mvm: fix an off-by-1 boundary check Before looking at the 11th byte, check the length is big enough.

    Product
    Linux
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Sep 23, 2026Unauthenticated Broken Access Control in Online Booking & Scheduling Calendar for WordPress by vcita <= 4.6.0 versions.CVE-2026-95513 · WordPress plugins & themes · reported by PatchstackHigh 7.5

    Unauthenticated Broken Access Control in Online Booking & Scheduling Calendar for WordPress by vcita <= 4.6.0 versions.

    Affected
    up to 4.6.0
    What to do
    Affects up to 4.6.0. Update the plugin to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Sep 23, 2026An out-of-bounds write vulnerability exists in the PDF rendering process of Foxit PDF Editor/Reader due to insufficient consistency and boundary validation whenCVE-2026-91794 · Other software · Foxit Software Inc. · reported by 14984358-7092-470d-8f34-ade47a7658a2High 7.8

    An out-of-bounds write vulnerability exists in the PDF rendering process of Foxit PDF Editor/Reader due to insufficient consistency and boundary validation when processing malformed color space data, which may cause the program to crash and potentially lead to remote code execution.

    Product
    Foxit PDF Editor
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Sep 23, 2026Booking Manager: Does not sanitize and escape values taken from a fetched external iCalendar feed before using them in a SQL queryCVE-2026-91024 · WordPress plugins & themes · reported by WPScanMedium 6.8

    The Booking Manager WordPress plugin before 2.1.21 does not sanitize and escape values taken from a fetched external iCalendar feed before using them in a SQL query, allowing authenticated users with Author-level access and above to perform SQL injection attacks by importing a feed they control.

    Product
    Booking Manager
    Fixed in
    2.1.21
    What to do
    Update Booking Manager to 2.1.21 or newer.
  • Sep 23, 2026Events Calendar: Does not perform a per-object capability check on one family of its REST write routesCVE-2026-84743 · WordPress plugins & themes · reported by WPScanLow 3.8

    The Events Calendar WordPress plugin before 6.17.5 does not perform a per-object capability check on one family of its REST write routes, allowing users with a low-privilege role such as contributor to modify, unpublish, trash and take ownership of records belonging to other users, including administrators.

    Product
    Events Calendar
    Fixed in
    6.17.5
    What to do
    Update Events Calendar to 6.17.5 or newer.
  • Sep 23, 2026Events Calendar: Does not check the capability required to publish content before creating or updating it through its REST APICVE-2026-84742 · WordPress plugins & themes · reported by WPScanLow 2.7

    The Events Calendar WordPress plugin before 6.17.5 does not check the capability required to publish content before creating or updating it through its REST API, allowing users with a role that cannot normally publish, such as contributor, to publish content directly and bypass editorial review.

    Product
    Events Calendar
    Fixed in
    6.17.5
    What to do
    Update Events Calendar to 6.17.5 or newer.
  • Sep 23, 2026Events Calendar: Does not check the post status of linked records before embedding their stored details into a public REST API responseCVE-2026-84741 · WordPress plugins & themes · reported by WPScanMedium 5.3

    The Events Calendar WordPress plugin before 6.17.5 does not check the post status of linked records before embedding their stored details into a public REST API response, allowing unauthenticated users to read the contents of records that have never been published.

    Product
    Events Calendar
    Fixed in
    6.17.5
    What to do
    Update Events Calendar to 6.17.5 or newer.

Where this comes from: the exploited list is CISA’s Known Exploited Vulnerabilities catalog. Everything else is the whole National Vulnerability Database, where each record is published by the team that found the bug (Wordfence, Patchstack, WPScan, the vendors themselves and others); we show who. Exploit odds are FIRST’s EPSS, updated daily. Titles and categories are ours, so check the linked record before acting on a detail. For a write-up of the big ones, see our advisories. Every vendor, and every WordPress plugin and theme with a recorded flaw, also has its own page. All of it is free to reuse as JSON, CSV or RSS.

Weekly security brief

The flaws that hit local websites, every Friday.

One short email: what got exploited this week, which WordPress plugins broke, and what to check. Unsubscribe in one click.

Get in touch

Tell us what you're building.

A website, your marketing, a security check, an app, or the thing you've been running out of a spreadsheet for three years. A few lines is plenty.

01The person who'll do the work writes back
02A short call, then a written plan with the price
03Nothing starts until you say yes
04Hacked or down right now? Call, and we pick up the same day
843-331-6339

Not ready to talk yet? Run the free website check and see what Google sees.

What do you need?
Build
Grow
Protect
Urgent

No newsletter, no sales sequence. Just a reply.