CVE Watch409.880 no arquivo completo

Vulnerabilidades exploráveis hoje

17,569na visualização atual

Score único que combina CVSS, presença no KEV e EPSS. Cada CVE com sua própria ficha — timeline da publicação até a exploração ativa.

No catálogo KEV1,769

Novos KEV · 24H0

Exploit Today ≥ 701,700

Distribuição · última janela

Crítica
5,508
Alta
20,914
Média
19,998
Baixa
2,058

Filtros

Janela

Severidade

Filtros

Vulnerabilidades5,761–5,800 · 17,569

CVECVSSEPSSKEVRExploitTítuloMod.

CVE-2026-116677—

7.0%

——2OpenWISP Controller is a network and WiFi controller for provisioning, configuration management, updates, and PKI management. From 1.0.0 until 1.3.2, the GET /api/v1/controller/ca/<integer-id>/crl endpoint allows an authenticated organization manager with CA view permission to retrieve another organization's certificate revocation list by requesting its sequential CA identifier. CrlDownloadView.retrieve resolves the CA directly instead of using the organization-scoped object retrieval enforced by FilterByOrganizationManaged, bypassing the endpoint's intended authorization boundary. The response can disclose CA issuer information and revoked certificate serial numbers, but it does not expose CA private keys or allow modification. This issue is fixed in version 1.3.2.6d CVE-2026-1166768.8 ALT

40.6%

——12Atlantis is a self-hosted golang application that listens for Terraform pull request events via webhooks. From version 0.4.0 until 0.47.1, Atlantis passes the pull-request-controlled workspace value from atlantis.yaml into Terraform command arguments that are joined with strings.Join(args, " ") and executed through sh -c. An authenticated contributor whose pull request is eligible for an Atlantis plan can include shell metacharacters in the workspace name, causing arbitrary commands to execute as the Atlantis service account without custom workflows, apply permission, or a malicious Terraform provider. External contributors can reach the flaw through fork pull requests only when --allow-fork-prs is enabled, while eligible same-repository branches do not require that option. The commands inherit the Atlantis process environment and can access cloud-provider, Terraform, and version-control credentials as well as files, state, and network resources available to the service. This issue is fixed in version 0.47.1.5d CVE-2026-1166627.5 ALT

31.7%

——10Tanium addressed a compression bomb vulnerability in Enforce.4d CVE-2026-1166604.3 MÉD

14.0%

——4Tanium addressed an improper access controls vulnerability in Enforce.4d CVE-2026-1166594.3 MÉD

23.2%

——7Tanium addressed an uncontrolled resource consumption vulnerability in Enforce.4d CVE-2026-1166586.5 MÉD

27.1%

——8Tanium addressed a denial of service vulnerability in Enforce.4d CVE-2026-1166575.3 MÉD

27.5%

——8Tanium addressed a denial of service vulnerability in Enforce.4d CVE-2026-1166567.5 ALT

31.7%

——10Tanium addressed an uncontrolled resource consumption vulnerability in Enforce.4d CVE-2026-1166497.1 ALT

10.2%

——3Tanium addressed an improper output sanitization vulnerability in Enforce.4d CVE-2026-1166477.1 ALT

15.5%

——5Tanium addressed an improper output sanitization vulnerability in Comply.4d CVE-2026-111054—

—

——0Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2026-112374. Reason: This candidate is a duplicate of CVE-2026-112374. Notes: All CVE users should reference CVE-2026-112374 instead of this candidate.12d CVE-2026-1083332.5 BAI

2.2%

——1Tanium addressed a use-after-free vulnerability in Threat Response Client Extension.4d CVE-2026-1083326.3 MÉD

4.1%

——1Tanium addressed an improper link resolution before file access vulnerability in Threat Response Client Extension.4d CVE-2026-1083313.3 BAI

3.6%

——1Tanium addressed an infinite loop vulnerability in Threat Response Client Extension.4d CVE-2026-1083303.6 BAI

2.4%

——1Tanium addressed an information disclosure vulnerability in Threat Response Client Extension.4d CVE-2026-1083298.8 ALT

42.8%

——13Tanium addressed an unauthorized code execution vulnerability in Threat Response.4d CVE-2026-1083284.2 MÉD

14.0%

——4Tanium addressed an insertion of sensitive information into log file vulnerability in Threat Response.4d CVE-2026-1083266.5 MÉD

7.1%

——2Tanium addressed an improper certificate validation vulnerability in Stream Client Extension.4d CVE-2026-1083256.6 MÉD

15.7%

——5Tanium addressed an insertion of sensitive information into log file vulnerability in Reputation.4d CVE-2026-1083164.3 MÉD

16.7%

——5Tanium addressed an information disclosure vulnerability in Tanium Server.4d CVE-2026-1083136.6 MÉD

23.0%

——7Tanium addressed an incorrect privilege assignment vulnerability in Tanium Server.4d CVE-2026-1083112.7 BAI

15.4%

——5Tanium addressed an insufficient logging vulnerability in Tanium Server.4d CVE-2026-1083105.3 MÉD

23.5%

——7Tanium addressed a denial of service vulnerability in Tanium Server.4d CVE-2026-1083095.5 MÉD

1.3%

——0Tanium addressed an uncontrolled resource consumption vulnerability in Performance Client Extension.4d CVE-2026-1083086.5 MÉD

29.1%

——9Tanium addressed a SQL injection vulnerability in Patch.4d CVE-2026-1083077.8 ALT

2.6%

——1Tanium addressed a heap-based buffer overflow vulnerability in Index.4d CVE-2026-1083067.8 ALT

3.1%

——1Tanium addressed a local privilege escalation vulnerability in End-User Notifications.4d CVE-2026-1083057.8 ALT

3.3%

——1Tanium addressed a local privilege escalation vulnerability in End-User Notifications.4d CVE-2026-1083047.8 ALT

1.9%

——1Tanium addressed a local privilege escalation vulnerability in End-User Notifications.4d CVE-2026-1083038.8 ALT

17.0%

——5Tanium addressed an unauthorized code execution vulnerability in Certificate Manager.4d CVE-2026-1083024.3 MÉD

6.3%

——2Tanium addressed an improper access controls vulnerability in Comply.4d CVE-2026-1083016.0 MÉD

3.0%

——1Tanium addressed an improper access controls vulnerability in Comply.4d CVE-2026-102816—

6.2%

——2An authorization vulnerability exists in the country or region configuration interface of TP-Link RE305 V3. An unauthenticated attacker on the same local network may modify the wireless regulatory region and force the device to reapply its wireless configuration. Successful exploitation may cause wireless connection interruptions, unavailable channels, client disconnections, or wireless service instability, and may cause the device to apply parameters intended for a different regulatory region.4d CVE-2026-102815—

48.9%

——15An operating-system command injection vulnerability exists in the tmpServer service of TP-Link RE305 V3. The service runs with root privileges and listens on the local loopback interface. A local attacker with access to a low-privileged process on the device may submit a crafted request to the TDDPv1 service and execute operating-system commands with root privileges. Successful exploitation may allow a local attacker with low privileges to obtain root privileges and execute arbitrary operating-system commands on the affected device.10d CVE-2026-102814—

29.9%

——9An authentication weakness exists in the TP-Link TDDP v2 service of TP-Link RE305 V3. TDDP v2 uses a fixed and derivable cryptographic key, which may allow an unauthenticated attacker on the same local network to forge protocol packets and access privileged TDDP operations, including functionality that can lead to operating-system command execution when the TDDP service is running and accessible. Successful exploitation may allow an unauthenticated attacker on the same local area network to execute arbitrary system commands with root privileges.10d CVE-2026-102813—

9.7%

——3An authentication flaw exists in the password-recovery functionality of TP-Link RE305 V3. The verification-code interface allows an unauthenticated attacker on the same local network to trigger generation of an administrator password-reset verification code. Because the interface lacks an effective attempt counter or lockout mechanism and uses a predictable verification-code generation process, an attacker may obtain or brute-force the code and reset the administrator password. Successful exploitation may allow an unauthenticated attacker on the local network to reset the administrator password and subsequently access privileged device-management functions.4d CVE-2026-102812—

1.8%

——1A hard-coded cryptographic key vulnerability exists in the user-configuration backup mechanism of TP-Link RE305 V3 and Archer C7 V5. A fixed AES-128 key and initialization vector are embedded in the firmware configuration-management component. An attacker who obtains an affected configuration backup file may extract the cryptographic material from the firmware and use it to decrypt the backup. Successful exploitation may disclose sensitive configuration information contained in a backup file, including administrator passwords and Wi-Fi credentials.4d CVE-2026-878974.6 MÉD

10.3%

——3A SSRF vulnerability found that enables access to internal Chrome Devtools Protocol APIs that can leak the JWT authentication token for another user. A low privileged attacker could continually exploit this vulnerability to leak the JWT authentication token for another user when they start a recording, which then enables the attacker read/write access to the victim's Whiteboard.4d CVE-2026-829864.6 MÉD

6.1%

——2The user in a group can bypass the group restriction set by an administrator on link sharing, creating share links for a table even though they shouldn't have that permission.4d CVE-2026-829844.3 MÉD

19.9%

——6When a team was configured as "visible to everyone", the web UI correctly blocked non-members from viewing the team ("You are not a member of ..."), but the resources API endpoint could still be called directly, allowing any authenticated non-member to enumerate the team's internal resources and their identifiers. This does not grant access to the contents of the discovered resources themselves, only their existence, names, and identifiers.4d