CVEs

Tenable maintains a list of Common Vulnerabilities and Exposures (CVEs) and their affected products. Tenable augments the data to include related Tenable Plugins that detect each vulnerability. 297651 CVEs are indexed from NVD.

Search

Vulnerability Watch ›

  • CVE-2025-49113
    criticalVulnerability of Interest

    This flaw has been reported to have been exploited in the wild. Roundcube users should update as soon as possible.

  • CVE-2025-48828
    criticalVulnerability of Interest

    While PoC exploits are available for CVE-2025-48827 and CVE-2025-48828, exploitation attempts have only been observed for CVE-2025-48827.

  • CVE-2025-48827
    criticalVulnerability of Interest

    While PoC exploits are available for CVE-2025-48827 and CVE-2025-48828, exploitation attempts have only been observed for CVE-2025-48827.

  • CVE-2025-20286
    criticalVulnerability Being Monitored

    Cisco notes that public exploit code is available. Immediate patching is recommended to ensure you are secure from this vulnerability.

  • CVE-2025-20130
    mediumVulnerability Being Monitored

    Cisco notes that public exploit code is available. Immediate patching is recommended to ensure you are secure from this vulnerability.

  • CVE-2025-20129
    mediumVulnerability Being Monitored

    Cisco notes that public exploit code is available. Immediate patching is recommended to ensure you are secure from this vulnerability.

  • CVE-2025-5419
    highVulnerability Being Monitored

    Google Threat Analysis Group (TAG) reports that this vulnerability was exploited in the wild as a zero-day. We're monitoring for additional details.

  • CVE-2025-3935
    highVulnerability Being Monitored

    According to Blackpoint Cyber, this flaw was reportedly exploited in the wild against ConnectWise. We are monitoring for further details, including additional confirmations.

  • CVE-2025-24893
    criticalVulnerability Being Monitored

    Public exploit code exists for this RCE vulnerability. Immediate patching is recommended.

Newest ›

  • A vulnerability has been found in Tenda AC9 15.03.02.13 and classified as critical. Affected by this vulnerability is the function formSetSafeWanWebMan of the file /goform/SetRemoteWebCfg of the component HTTP POST Request Handler. The manipulation of the argument remoteIp leads to stack-based buffer overflow. The attack can be launched remotely. The exploit has been disclosed to the public and may be used.

  • in OpenHarmony v5.0.3 and prior versions allow a local attacker cause information leak through get permission.

  • in OpenHarmony v5.0.3 and prior versions allow a local attacker cause information leak through get permission.

  • in OpenHarmony v5.0.3 and prior versions allow a local attacker cause DOS through improper input.

  • in OpenHarmony v5.0.3 and prior versions allow a local attacker cause DOS through improper input.

  • in OpenHarmony v5.0.3 and prior versions allow a local attacker cause information leak through get permission.

  • in OpenHarmony v5.0.3 and prior versions allow a local attacker cause information leak through get permission.

  • in OpenHarmony v5.0.3 and prior versions allow a local attacker case DOS through NULL pointer dereference.

  • in OpenHarmony v5.0.3 and prior versions allow a local attacker cause information leak through race condition.

  • in OpenHarmony v5.0.3 and prior versions allow a local attacker cause DOS through out-of-bounds read.

Updated ›

  • A vulnerability has been found in Tenda AC9 15.03.02.13 and classified as critical. Affected by this vulnerability is the function formSetSafeWanWebMan of the file /goform/SetRemoteWebCfg of the component HTTP POST Request Handler. The manipulation of the argument remoteIp leads to stack-based buffer overflow. The attack can be launched remotely. The exploit has been disclosed to the public and may be used.

  • In the Linux kernel, the following vulnerability has been resolved: can: bcm: add locking for bcm_op runtime updates The CAN broadcast manager (CAN BCM) can send a sequence of CAN frames via hrtimer. The content and also the length of the sequence can be changed resp reduced at runtime where the 'currframe' counter is then set to zero. Although this appeared to be a safe operation the updates of 'currframe' can be triggered from user space and hrtimer context in bcm_can_tx(). Anderson Nascimento created a proof of concept that triggered a KASAN slab-out-of-bounds read access which can be prevented with a spin_lock_bh. At the rework of bcm_can_tx() the 'count' variable has been moved into the protected section as this variable can be modified from both contexts too.

  • In the Linux kernel, the following vulnerability has been resolved: can: bcm: add missing rcu read protection for procfs content When the procfs content is generated for a bcm_op which is in the process to be removed the procfs output might show unreliable data (UAF). As the removal of bcm_op's is already implemented with rcu handling this patch adds the missing rcu_read_lock() and makes sure the list entries are properly removed under rcu protection.

  • in OpenHarmony v5.0.3 and prior versions allow a local attacker cause information leak through get permission.

  • in OpenHarmony v5.0.3 and prior versions allow a local attacker cause information leak through get permission.

  • in OpenHarmony v5.0.3 and prior versions allow a local attacker cause DOS through improper input.

  • in OpenHarmony v5.0.3 and prior versions allow a local attacker cause DOS through improper input.

  • in OpenHarmony v5.0.3 and prior versions allow a local attacker cause information leak through get permission.

  • in OpenHarmony v5.0.3 and prior versions allow a local attacker cause information leak through get permission.

  • in OpenHarmony v5.0.3 and prior versions allow a local attacker case DOS through NULL pointer dereference.