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 34 min 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,762exploited flaws on CISA’s list
34added in the last 30 days
353new WordPress flaws this week
390,080entries in the database

1,326 results · page 3 of 27

  • Oct 2, 2026Access of Uninitialized Pointer vulnerability in Apache Thrift c_glib bindings.CVE-2026-66081 · Websites & servers · Apache Software Foundation · reported by security@apache.orgHigh 8.7

    Access of Uninitialized Pointer vulnerability in Apache Thrift c_glib 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, 2026Allocation of Resources Without Limits or Throttling vulnerability in Apache Thrift C++, Java, Go, netstd, Python and Delphi bindings.CVE-2026-66055 · Websites & servers · Apache Software Foundation · reported by security@apache.orgHigh 8.2

    Allocation of Resources Without Limits or Throttling vulnerability in Apache Thrift C++, Java, Go, netstd, Python and Delphi 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, 2026Allocation of Resources Without Limits or Throttling, Improper Handling of Highly Compressed Data (Data Amplification) vulnerability in Apache Thrift C++ bindinCVE-2026-66054 · Websites & servers · Apache Software Foundation · reported by security@apache.orgMedium 6.9

    Allocation of Resources Without Limits or Throttling, Improper Handling of Highly Compressed Data (Data Amplification) vulnerability in Apache Thrift C++ 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, 2026Allocation of Resources Without Limits or Throttling vulnerability in Apache Thrift go bindings.CVE-2026-63772 · Websites & servers · Apache Software Foundation · reported by security@apache.orgHigh 8.7

    Allocation of Resources Without Limits or Throttling vulnerability in Apache Thrift go 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, 2026Allocation of Resources Without Limits or Throttling vulnerability in Apache Thrift Java bindings.CVE-2026-61374 · Websites & servers · Apache Software Foundation · reported by security@apache.orgHigh 7.1

    Allocation of Resources Without Limits or Throttling vulnerability in Apache Thrift Java 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, 2026Uncaught exception, Improper Handling of Exceptional Conditions vulnerability in Apache Thrift NodeJS bindings.CVE-2026-96294 · Websites & servers · Apache Software Foundation · reported by security@apache.orgHigh 8.7

    Uncaught exception, Improper Handling of Exceptional Conditions vulnerability in Apache Thrift NodeJS 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, 2026Inefficient regular expression complexity, Inefficient Algorithmic Complexity vulnerability in Apache Thrift Lua bindings.CVE-2026-96292 · Websites & servers · Apache Software Foundation · reported by security@apache.orgHigh 8.2

    Inefficient regular expression complexity, Inefficient Algorithmic Complexity vulnerability in Apache Thrift Lua 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, Allocation of resources without limits or throttling vulnerability in Apache Thrift Erlang bindings.CVE-2026-96288 · Websites & servers · Apache Software Foundation · reported by security@apache.orgHigh 8.2

    Uncontrolled Recursion, Allocation of resources without limits or throttling vulnerability in Apache Thrift Erlang 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, 2026Inefficient Algorithmic Complexity vulnerability in Apache Thrift PHP bindings.CVE-2026-94653 · Websites & servers · Apache Software Foundation · reported by security@apache.orgHigh 8.2

    Inefficient Algorithmic Complexity vulnerability in Apache Thrift PHP 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, 2026Missing release of memory after effective lifetime vulnerability in Apache Thrift c++ bindings.CVE-2026-94652 · Websites & servers · Apache Software Foundation · reported by security@apache.orgMedium 6.3

    Missing release of memory after effective lifetime vulnerability in Apache Thrift c++ 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, 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, 2026Allocation of resources without limits or throttling vulnerability in Apache Thrift PHP bindings.CVE-2026-94638 · Websites & servers · Apache Software Foundation · reported by security@apache.orgMedium 6.3

    Allocation of resources without limits or throttling vulnerability in Apache Thrift PHP 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, 2026Improper handling of highly compressed data (data amplification) vulnerability in Apache Thrift Go bindings.CVE-2026-94637 · Websites & servers · Apache Software Foundation · reported by security@apache.orgHigh 8.2

    Improper handling of highly compressed data (data amplification) vulnerability in Apache Thrift Go 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, 2026NULL pointer dereference vulnerability in Apache Thrift PHP bindings.CVE-2026-87117 · Websites & servers · Apache Software Foundation · reported by security@apache.orgHigh 8.7

    NULL pointer dereference vulnerability in Apache Thrift PHP 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, 2026Improperly controlled modification of object prototype attributes ('prototype pollution') vulnerability in Apache Thrift all JS bindings.CVE-2026-86536 · Websites & servers · Apache Software Foundation · reported by security@apache.orgMedium 6.3

    Improperly controlled modification of object prototype attributes ('prototype pollution') vulnerability in Apache Thrift all JS bindings. This issue affects Apache Thrift: before 0.25.0. Users are recommended to upgrade to version 0.25.0 and re-generate JS code, which fixes the issue.

    Product
    Apache Thrift
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Oct 2, 2026Improper certificate validation, Return of wrong status code vulnerability in Apache Thrift python bindings.CVE-2026-85087 · Websites & servers · Apache Software Foundation · reported by security@apache.orgMedium 6.9

    Improper certificate validation, Return of wrong status code vulnerability in Apache Thrift python 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, 2026Improper certificate validation, Initialization of a resource with an insecure default vulnerability in Apache Thrift perl bindings.CVE-2026-85086 · Websites & servers · Apache Software Foundation · reported by security@apache.orgMedium 6.9

    Improper certificate validation, Initialization of a resource with an insecure default vulnerability in Apache Thrift perl 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, 2026YesWiki before 4.6.7 contains an authentication bypass vulnerability in the ActivityPub inbox that fails to bind the verified HTTP signature signer to the activCVE-2026-104445 · Other software · YesWiki · reported by VulnCheckHigh 8.8

    YesWiki before 4.6.7 contains an authentication bypass vulnerability in the ActivityPub inbox that fails to bind the verified HTTP signature signer to the activity actor. Unauthenticated attackers with any ActivityPub keypair can send signed Delete or Update activities referencing a mirrored entry's sourceUrl to delete or overwrite other actors' federated entries.

    Product
    yeswiki
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Oct 2, 2026Allocation of Resources Without Limits or Throttling vulnerability in Apache Thrift Erlang bindings.CVE-2026-96990 · Websites & servers · Apache Software Foundation · reported by security@apache.orgHigh 8.2

    Allocation of Resources Without Limits or Throttling vulnerability in Apache Thrift Erlang 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, 2026improper handling of exceptional conditions, Missing release of resource after effective lifetime vulnerability in Apache Thrift java bindings.CVE-2026-94651 · Websites & servers · Apache Software Foundation · reported by security@apache.orgHigh 8.2

    improper handling of exceptional conditions, Missing release of resource after effective lifetime vulnerability in Apache Thrift java 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 c_glib bindings.CVE-2026-94650 · Websites & servers · Apache Software Foundation · reported by security@apache.orgHigh 8.2

    Uncontrolled Recursion vulnerability in Apache Thrift c_glib 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, 2026Improper validation of specified quantity in input, Allocation of resources without limits or throttling vulnerability in Apache Thrift nodejs bindings.CVE-2026-94645 · Websites & servers · Apache Software Foundation · reported by security@apache.orgHigh 8.2

    Improper validation of specified quantity in input, Allocation of resources without limits or throttling vulnerability in Apache Thrift nodejs 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, 2026Allocation of resources without limits or throttling vulnerability in Apache Thrift PHP bindings.CVE-2026-94644 · Websites & servers · Apache Software Foundation · reported by security@apache.orgHigh 8.2

    Allocation of resources without limits or throttling vulnerability in Apache Thrift PHP 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, 2026Uncaught exception vulnerability in Apache Thrift PHP bindings.CVE-2026-94642 · Websites & servers · Apache Software Foundation · reported by security@apache.orgHigh 8.7

    Uncaught exception vulnerability in Apache Thrift PHP 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, 2026Use of uninitialized resource, Return of wrong status code vulnerability in Apache Thrift c_glib bindings.CVE-2026-85483 · Websites & servers · Apache Software Foundation · reported by security@apache.orgMedium 6.3

    Use of uninitialized resource, Return of wrong status code vulnerability in Apache Thrift c_glib 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, 2026improper handling of exceptional conditions, Allocation of resources without limits or throttling, Uncaught exception vulnerability in Apache Thrift Java bindinCVE-2026-94639 · Websites & servers · Apache Software Foundation · reported by security@apache.orgHigh 8.2

    improper handling of exceptional conditions, Allocation of resources without limits or throttling, Uncaught exception vulnerability in Apache Thrift Java 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, 2026Allocation of resources without limits or throttling, Improper handling of length parameter inconsistency vulnerability in Apache Thrift Lua bindings.CVE-2026-94635 · Websites & servers · Apache Software Foundation · reported by security@apache.orgHigh 8.7

    Allocation of resources without limits or throttling, Improper handling of length parameter inconsistency vulnerability in Apache Thrift Lua 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, 2026Allocation of resources without limits or throttling, Initialization of a resource with an insecure default vulnerability in Apache Thrift Python bindings.CVE-2026-94634 · Websites & servers · Apache Software Foundation · reported by security@apache.orgHigh 8.2

    Allocation of resources without limits or throttling, Initialization of a resource with an insecure default vulnerability in Apache Thrift Python 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 1, 2026Authlib version 1.7.2 and below contains a vulnerability where discovery JSON metadata is cached without validation or issuer-origin binding.CVE-2026-104056 · Other software · Authlib · reported by cret@cert.orgCritical 9.8

    Authlib version 1.7.2 and below contains a vulnerability where discovery JSON metadata is cached without validation or issuer-origin binding. This allows a poisoned discovery response to replace all endpoint values with attacker-controlled values rather than endpoint URLs that share the origin of the configured server metadata URL.

    Product
    Authlib
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Sep 29, 2026Use after free in Bindings in Google Chrome prior to 154.0.8037.57 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML pagCVE-2026-95353 · Computers, phones & browsers · Google · reported by chrome-cve-admin@google.comHigh 8.8

    Use after free in Bindings in Google Chrome prior to 154.0.8037.57 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: Medium)

    Product
    Chrome
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Sep 29, 2026Type confusion in Bindings in Google Chrome prior to 154.0.8037.57 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML pagCVE-2026-95286 · Computers, phones & browsers · Google · reported by chrome-cve-admin@google.comHigh 8.8

    Type confusion in Bindings in Google Chrome prior to 154.0.8037.57 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High)

    Product
    Chrome
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Sep 29, 2026The mechanism binding API-uploaded files to the uploader's authentication method is not working correctly and the same session token is used for all token-basedCVE-2026-101269 · Other software · pretix · reported by 655498c3-6ec5-4f0b-aea6-853b334d05a6Low 2.3

    The mechanism binding API-uploaded files to the uploader's authentication method is not working correctly and the same session token is used for all token-based API users. Since API-uploaded files are refered to by randomly generated UUIDs and only exist for a day, there is virtually no risk, but it renders the added protection mechanism useless.

    Product
    pretix
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Sep 27, 2026Penpot before 2.18.0 binds the MCP server plugin WebSocket bridge to all network interfaces without authentication in single-user mode.CVE-2026-100868 · Other software · penpot · reported by VulnCheckMedium 5.3

    Penpot before 2.18.0 binds the MCP server plugin WebSocket bridge to all network interfaces without authentication in single-user mode. Unauthenticated attackers on adjacent networks can connect to the WebSocket port to impersonate the Penpot browser plugin, intercept task payloads, and return forged results to the MCP client.

    Product
    penpot
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Sep 26, 2026Capgo (capgo.app backend) before 12.127.5 contains an authorization flaw in the PATCH /private/role_bindings/:binding_id endpoint.CVE-2026-100629 · Other software · Cap-go · reported by VulnCheckHigh 7

    Capgo (capgo.app backend) before 12.127.5 contains an authorization flaw in the PATCH /private/role_bindings/:binding_id endpoint. The handler verifies that the newly assigned role's priority rank does not exceed the caller's own rank, but — unlike the DELETE handler — it never checks the rank of the role currently bound to the target binding. An authenticated user holding the org_admin role (rank 90) can therefore change an org_super_admin binding (rank 95) to a lower-privileged role such as org_member (rank 75). Because the prevent_last_super_admin_binding_delete database trigger fires only BEFORE DELETE and not on UPDATE, an org_admin can demote every org_super_admin, leaving the organization with no super administrator. The issue is fixed in 12.127.5.

    Product
    capgo.app
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Sep 26, 2026Capgo (capgo.app backend, versions ≤ 12.261.0) improperly restricts which roles the apikey_manager organization role may bind to newly created API keys.CVE-2026-100611 · Other software · Cap-go · reported by VulnCheckHigh 7.1

    Capgo (capgo.app backend, versions ≤ 12.261.0) improperly restricts which roles the apikey_manager organization role may bind to newly created API keys. When an authenticated user holding only apikey_manager (permissions org.manage_apikeys and org.read) calls POST /apikey with a JWT session, the only checks applied are the org.manage_apikeys permission, a fixed deny-list of assignable role names (APIKEY_MANAGER_DENIED_ASSIGNABLE_ROLES in public/apikey/scope.ts), and a priority-rank comparison in createRoleBindingForPrincipal (private/role_bindings.ts). No check verifies that the caller actually holds the permissions conferred by the role being assigned. Because the deny-list omits the deploy roles app_developer, app_uploader, channel_developer and channel_uploader, and apikey_manager is seeded with priority_rank 78 — higher than those roles' ranks (68, 66, 58, 57) — the rank check also passes. As a result, an apikey_manager who cannot upload bundles or promote channels can mint an API key bound to a deploy role and use it to push arbitrary OTA JavaScript updates to all end users of the organization's apps. As of the advisory publication no patched version was available.

    Product
    capgo.app
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Sep 26, 2026Flowise through 3.1.4 resolves SSO and local-password users solely by email without storing provider or subject identifier bindings, allowing attackers to autheCVE-2026-100607 · Other software · FlowiseAI · reported by VulnCheckCritical 9.2

    Flowise through 3.1.4 resolves SSO and local-password users solely by email without storing provider or subject identifier bindings, allowing attackers to authenticate as any existing user by claiming their email at any configured SSO provider. Attackers can gain complete account access including chatflows, credentials, and API keys by authenticating through a different SSO provider or local password than the victim's original registration method.

    Product
    Flowise
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Sep 26, 2026ClawHub (the openclaw/clawhub application/backend) does not bind anonymous HTTP API requests to a trusted caller identity, so all direct anonymous API requests CVE-2026-100600 · Other software · openclaw · reported by VulnCheckMedium 6.9

    ClawHub (the openclaw/clawhub application/backend) does not bind anonymous HTTP API requests to a trusted caller identity, so all direct anonymous API requests share a single default quota allowance. A remote, unauthenticated caller can drain that shared allowance and thereby deny or degrade API access for unrelated visitors. In addition, when the TRUST_FORWARDED_IPS option is enabled without an authenticated edge/proxy, clients can supply arbitrary forwarded IP headers to select quota identities of their choosing and evade rate limiting. The issue was confirmed at revision cbfee7343ddc867316dd9b3de6fa8856730f9f41; the complete historical affected range was not established. It is fixed in revision 8c2de6c506bb4efabe3f0c2ffb8370b9e23d4650 (PR #3684), where direct anonymous calls are redirected to the public API origin without consuming quota and forged identity assertions return HTTP 401. The npm CLI and OpenClaw runtime are separate products and are not affected.

    Product
    clawhub
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Sep 25, 2026OpenClaw (npm package openclaw) before 2026.7.1 incorrectly binds Signal approval reactions.CVE-2026-100598 · Other software · OpenClaw · reported by VulnCheckHigh 7.5

    OpenClaw (npm package openclaw) before 2026.7.1 incorrectly binds Signal approval reactions. In affected versions, a reaction intended to resolve a structured approval request could instead attach to ordinary outbound text when unrelated outbound messages and a pending approval are present in the same conversation. As a result, an approver's reaction to unrelated text could be interpreted as approving or denying a pending host action; the practical impact depends on the pending request, conversation timing, and the actions available to the OpenClaw process. The issue does not change the authority of correctly identified approvers. This is fixed in version 2026.7.1.

    Product
    OpenClaw
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Sep 25, 2026OpenClaw Codex before 2026.7.1 fails to properly enforce owner authorization when creating native conversation bindings.CVE-2026-100586 · Other software · OpenClaw · reported by VulnCheckHigh 8.7

    OpenClaw Codex before 2026.7.1 fails to properly enforce owner authorization when creating native conversation bindings. Non-owner channel senders with command access can create bindings to the native Codex runtime and execute host-capable turns with access to files, tools, and processes.

    Product
    OpenClaw
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Sep 25, 2026OpenClaw versions before 2026.8.1 fail to bind working directory context to reusable exec approvals, allowing approved commands to execute in different directorCVE-2026-100530 · Other software · OpenClaw · reported by VulnCheckHigh 8.5

    OpenClaw versions before 2026.8.1 fail to bind working directory context to reusable exec approvals, allowing approved commands to execute in different directories. Attackers with an allow-always approval can reuse it to run the same command against unreviewed files or repositories with materially different effects.

    Product
    OpenClaw
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Sep 25, 2026In the Linux kernel, the following vulnerability has been resolved: net: macb: fix NULL pointer dereference on unbind with fixed-link When the device tree desCVE-2026-98008 · Computers, phones & browsers · Linux · reported by 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    In the Linux kernel, the following vulnerability has been resolved: net: macb: fix NULL pointer dereference on unbind with fixed-link When the device tree describes a fixed-link and has no "mdio" child node, macb_mii_init() returns early without allocating the MDIO bus, leaving bp->mii_bus as NULL. Two cleanup paths then dereference this NULL bus: 1. On driver unbind, macb_remove() unconditionally calls mdiobus_unregister(bp->mii_bus), which oopses: Unable to handle kernel NULL pointer dereference at virtual address 00000000000004a8 pc : mdiobus_unregister+0x14/0xa4 lr : macb_remove+0x38/0xa4 Call trace: mdiobus_unregister+0x14/0xa4 (P) macb_remove+0x38/0xa4 platform_remove+0x20/0x30 device_release_driver_internal+0x1c8/0x224 unbind_store+0xb4/0xbc 2. On the probe error path in macb_probe(), reached when macb_mii_init() has succeeded but a subsequent step fails, the err_out_unregister_mdio label runs the same unconditional cleanup. mdiobus_unregister() and mdiobus_free() do not guard against a NULL bus, so guard the calls in both macb_remove() and the probe error path.

    Product
    Linux
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Sep 25, 2026Rojo's "rojo serve" HTTP API (default port 34872) has no Host/Origin header validation, making it vulnerable to DNS rebinding.CVE-2026-97875 · Other software · rojo-rbx · reported by 74b3a70d-cca6-4d34-9789-e83b222ae3beHigh 8.1

    Rojo's "rojo serve" HTTP API (default port 34872) has no Host/Origin header validation, making it vulnerable to DNS rebinding. A malicious webpage can read all project source, write malicious code to files on disk, and launch local programs via opener::open() with no user interaction beyond visiting the page.

    Product
    rojo
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Sep 25, 2026Keycloak provides a feature called mTLS holder-of-key binding which ensures that a token can only be used by the client that originally requested it by binding CVE-2026-97846 · Other software · Red Hat · reported by Red HatMedium 6.8

    Keycloak provides a feature called mTLS holder-of-key binding which ensures that a token can only be used by the client that originally requested it by binding it to their digital certificate. A flaw was discovered where the new Standard Token Exchange V2 feature does not check for this certificate. This allows an attacker with stolen client credentials to obtain a standard, unrestricted token that bypasses these security protections.

    Product
    Red Hat Build of Keycloak
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Sep 24, 2026The Botslab G980H dash camera firmware does not require authenticated pairing or client binding before permitting access to Bluetooth Low Energy communications CVE-2026-84403 · Other software · Botslab · reported by ics-cert@hq.dhs.govMedium 6.9

    The Botslab G980H dash camera firmware does not require authenticated pairing or client binding before permitting access to Bluetooth Low Energy communications and GATT characteristics. An unauthenticated attacker within Bluetooth range could intercept or directly retrieve sensitive device information, including device identifiers, firmware information, and protected WiFi credentials.

    Product
    G980H
    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: driver core: Avoid warning when removing a device while its supplier is unbinding During dCVE-2026-97479 · Computers, phones & browsers · Linux · reported by 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    In the Linux kernel, the following vulnerability has been resolved: driver core: Avoid warning when removing a device while its supplier is unbinding During driver removal, the following warning can appear: WARNING: CPU: 1 PID: 139 at drivers/base/core.c:1497 __device_links_no_driver+0xcc/0xfc ... Call trace: __device_links_no_driver+0xcc/0xfc (P) device_links_driver_cleanup+0xa8/0xf0 device_release_driver_internal+0x208/0x23c device_links_unbind_consumers+0xe0/0x108 device_release_driver_internal+0xec/0x23c device_links_unbind_consumers+0xe0/0x108 device_release_driver_internal+0xec/0x23c device_links_unbind_consumers+0xe0/0x108 device_release_driver_internal+0xec/0x23c driver_detach+0xa0/0x12c bus_remove_driver+0x6c/0xbc driver_unregister+0x30/0x60 pci_unregister_driver+0x20/0x9c lan966x_pci_driver_exit+0x18/0xa90 [lan966x_pci] This warning is triggered when a consumer is removed because the links status of its supplier is not DL_DEV_DRIVER_BOUND and the link flag DL_FLAG_SYNC_STATE_ONLY is not set. The topology in terms of consumers/suppliers used was the following (consumer ---> supplier):

    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/counter: Fix num_counters leak on bind_qp failure in alloc_and_bind() When __rdma_couCVE-2026-97477 · Computers, phones & browsers · Linux · reported by 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    In the Linux kernel, the following vulnerability has been resolved: RDMA/counter: Fix num_counters leak on bind_qp failure in alloc_and_bind() When __rdma_counter_bind_qp() fails in alloc_and_bind(), the error path jumps to err_mode which frees the counter without decrementing port_counter->num_counters. The only place that decrements is rdma_counter_free(), which is unreachable since the counter was never successfully bound. This leak accumulates across repeated failures, permanently preventing the port from switching to AUTO mode (-EBUSY in __counter_set_mode()) and blocking the MANUAL→NONE auto-revert in rdma_counter_free(). When the mode was NONE before the call, the MANUAL mode set by __counter_set_mode() also leaks since the revert logic is never reached. Add an err_bind label between the num_counters increment and the existing err_mode label. It decrements num_counters and mirrors the MANUAL→NONE revert from rdma_counter_free(), ensuring the port state is fully restored on bind failure.

    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 P2P-Device binding handling Our binding handling for P2P-Device caCVE-2026-97432 · 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 P2P-Device binding handling Our binding handling for P2P-Device can run into the following scenario, as observed by our testing: - a station interface is connected on some channel - the P2P-Device does a remain-on-channel (ROC) on that channel - the ROC ends, and the P2P-Device is removed from the binding, but the phy_ctxt pointer is left around as a PHY cache so we don't need to recalibrate to the channel again and again in case it's not shared - a binding update by the station interface, even a removal, will re-add the P2P-Device to the binding - the P2P-Device is removed, which removes the PHY context, but it's still in the binding so the firmware crashes Since the P2P device is removed from the binding and only re- added by unrelated code, but we want to keep the phy_ctxt around as a cache for future ROC usage, fix it by adding a boolean that indicates whether or not the P2P-Device should be added to the binding, and handle that in the binding iterator. That way, the station interface cannot re-add the P2P-Device to the binding when that isn't active.

    Product
    Linux
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Sep 23, 2026alsa-lib through 1.2.16.1 contains a denial of service vulnerability in the multi PCM plugin that fails to validate sparse binding indices before array access.CVE-2026-96675 · Other software · ALSA Project · reported by VulnCheckMedium 4.8

    alsa-lib through 1.2.16.1 contains a denial of service vulnerability in the multi PCM plugin that fails to validate sparse binding indices before array access. Attackers can supply a malicious ALSA configuration file with sparse bindings to trigger an out-of-bounds array read and assertion failure, causing the application to abort.

    Product
    alsa-lib
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.

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.