Vulnerabilidades explotables hoy
413,805en 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,779
Nuevos KEV · 24H0
Exploit Today ≥ 701,707
Distribución · última ventana
- Crítico5,594
- Alto22,456
- Medio20,780
- Bajo2,126
Filtros
Ventana
Severidad
Filtros
CVECVSSEPSSKEVRExplotTítuloVis.
CVE-2023-45136—92.8%
——28——CVE-2015-4509—92.8%
——28——CVE-2013-5458—92.8%
——28——CVE-2013-1736—92.8%
——28——CVE-2016-0703—92.8%
——28——CVE-2015-7801—92.8%
——28——CVE-2020-0637—92.8%
——28——CVE-2021-43799—92.8%
——28——CVE-2021-229255.3 MED92.8%
——28curl supports the `-t` command line option, known as `CURLOPT_TELNETOPTIONS`in libcurl. This rarely used option is used to send variable=content pairs toTELNET servers.Due to flaw in the option parser for sending `NEW_ENV` variables, libcurlcould be made to pass on uninitialized data from a stack based buffer to theserver. Therefore potentially revealing sensitive internal information to theserver using a clear-text network protocol.This could happen because curl did not call and use sscanf() correctly whenparsing the string provided by the application.30dCVE-2016-90639.8 CRÍ92.8%
——28An integer overflow during the parsing of XML using the Expat library. This vulnerability affects Firefox < 50.35dCVE-2026-434997.8 ALT92.8%
——28In the Linux kernel, the following vulnerability has been resolved:
rtmutex: Use waiter::task instead of current in remove_waiter()
remove_waiter() is used by the slowlock paths, but it is also used for
proxy-lock rollback in rt_mutex_start_proxy_lock() when invoked from
futex_requeue().
In the latter case waiter::task is not current, but remove_waiter()
operates on current for the dequeue operation. That results in several
problems:
1) the rbtree dequeue happens without waiter::task::pi_lock being held
2) the waiter task's pi_blocked_on state is not cleared, which leaves a
dangling pointer primed for UAF around.
3) rt_mutex_adjust_prio_chain() operates on the wrong top priority waiter
task
Use waiter::task instead of current in all related operations in
remove_waiter() to cure those problems.
[ tglx: Fixup rt_mutex_adjust_prio_chain(), add a comment and amend the
changelog ]2dCVE-2009-0195—92.8%
——28——CVE-2021-39847—92.8%
——28——CVE-2007-4060—92.8%
——28——CVE-2004-1717—92.8%
——28——CVE-2014-0526—92.8%
——28——CVE-2015-3245—92.8%
——28——CVE-2018-20242—92.8%
——28——CVE-2013-0754—92.8%
——28——CVE-2021-39821—92.8%
——28——CVE-2017-3142—92.8%
——28——CVE-2008-2111—92.8%
——28——CVE-2018-10757—92.8%
——28——CVE-2022-22836—92.8%
——28——CVE-2009-3379—92.8%
——28——CVE-2014-4947—92.8%
——28——CVE-2017-16361—92.8%
——28——CVE-2019-1301—92.8%
——28——CVE-2013-3333—92.8%
——28——CVE-2016-1111—92.8%
——28——CVE-2008-5266—92.8%
——28——CVE-2013-3334—92.8%
——28——CVE-2020-9410—92.8%
——28——CVE-2011-4074—92.8%
——28——CVE-2010-1209—92.8%
——28——CVE-2017-10949—92.8%
——28——CVE-2013-0263—92.8%
——28——CVE-2007-0736—92.8%
——28——CVE-2020-27956—92.8%
——28——CVE-2015-6544—92.8%
——28——