Vulnerabilidades explotables hoy
407,950en la vista actual
Score único combinando CVSS, membresía KEV y EPSS. Cada CVE con su ficha propia — timeline desde publicación hasta explotación activa.
En catálogo KEV1,767
Nuevos KEV · 24H0
Exploit Today ≥ 701,698
Distribución · última ventana
- Crítico5,761
- Alto22,437
- Medio20,906
- Bajo2,191
Filtros
Ventana
Severidad
Filtros
CVECVSSEPSSKEVRExplotTítuloVis.
CVE-2016-0036—96.0%
——29——CVE-2023-46259—96.0%
——29——CVE-2022-25347—96.0%
——29——CVE-2018-15120—96.0%
——29——CVE-2014-9148—96.0%
——29——CVE-2011-1894—96.0%
——29——CVE-2013-6407—96.0%
——29——CVE-2006-3876—96.0%
——29——CVE-2019-9189—96.0%
——29——CVE-2002-2100—96.0%
——29——CVE-2001-0723—96.0%
——29——CVE-2014-1881—96.0%
——29——CVE-2002-0242—96.0%
——29——CVE-2003-0276—96.0%
——29——CVE-2018-4068—96.0%
——29——CVE-2019-1102—96.0%
——29——CVE-2025-3663—96.0%
——29——CVE-2013-6877—96.0%
——29——CVE-2026-274469.8 CRÍ96.0%
——29Missing Authentication for Critical Function (CWE-306) vulnerability in Apache Artemis, Apache ActiveMQ Artemis. An unauthenticated remote attacker can use the Core protocol to force a target broker to establish an outbound Core federation connection to an attacker-controlled rogue broker. This could potentially result in message injection into any queue and/or message exfiltration from any queue via the rogue broker. This impacts environments that allow both:
- incoming Core protocol connections from untrusted sources to the broker
- outgoing Core protocol connections from the broker to untrusted targets
This issue affects:
- Apache Artemis from 2.50.0 through 2.51.0
- Apache ActiveMQ Artemis from 2.11.0 through 2.44.0.
Users are recommended to upgrade to Apache Artemis version 2.52.0, which fixes the issue.
The issue can be mitigated by one of the following:
- Remove Core protocol support from any acceptor receiving connections from untrusted sources. Incoming Core protocol connections are supported by default via the "artemis" acceptor listening on port 61616. See the "protocols" URL parameter configured for the acceptor. An acceptor URL without this parameter supports all protocols by default, including Core.
- Use two-way SSL (i.e. certificate-based authentication) in order to force every client to present the proper SSL certificate when establishing a connection before any message protocol handshake is attempted. This will prevent unauthenticated exploitation of this vulnerability.
- Implement and deploy a Core interceptor to deny all Core downstream federation connect packets. Such packets have a type of (int) -16 or (byte) 0xfffffff0. Documentation for interceptors is available at https://artemis.apache.org/components/artemis/documentation/latest/intercepting-operations.html .48dCVE-2015-3081—96.0%
——29——CVE-2022-0952—96.0%
——29——CVE-2012-0551—96.0%
——29——CVE-2010-1199—96.0%
——29——CVE-2025-151378.8 ALT96.0%
——29A vulnerability was detected in TRENDnet TEW-800MB 1.0.1.0. Affected by this vulnerability is the function sub_F934 of the file NTPSyncWithHost.cgi. The manipulation results in command injection. The attack may be launched remotely. The exploit is now public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.29dCVE-2021-26117—96.0%
——29——CVE-2019-13462—96.0%
——29——CVE-2016-2210—96.0%
——29——CVE-2020-24365—96.0%
——29——CVE-2004-0503—96.0%
——29——CVE-2007-0126—96.0%
——29——CVE-2013-4788—96.0%
——29——CVE-2019-6989—96.0%
——29——CVE-2021-264329.8 CRÍ96.0%
——29Windows Services for NFS ONCRPC XDR Driver Remote Code Execution Vulnerability87dCVE-2021-25294—96.0%
——29——CVE-2010-1878—96.0%
——29——CVE-2026-26119—96.0%
——29——CVE-2000-0506—96.0%
——29——CVE-2026-21249—96.0%
——29——CVE-2019-15889—96.0%
——29——CVE-2014-2730—96.0%
——29——