Seguridad de la Información

Alertas de Seguridad de la Información

Vulnerabilidades explotadas activamente, incidentes y análisis relevantes para México y LATAM. Actualizado automáticamente desde fuentes oficiales.

48 vulnerabilidades en CISA KEV — explotación activa confirmada Ver todas →

Última alerta publicada hace 11 min

13,434

Total alertas

3054

Críticas

10108

Altas

8

Ransomware

1740

Esta semana

RSS

Vulnerabilidades × haxx × Limpiar todo ×

H Crítico vulnerabilidad

[CVE-2026-8926] When asking curl to use a `.netrc` file to find credentials and at the same time specifying a URL wi…

When asking curl to use a `.netrc` file to find credentials and at the same time specifying a URL with a username(without a password), like `https://user@example.com/`, curl could wrongly get and use the password for *another* user set in the `.netrc` file for that host if such a one exists and there is no match for the specified user.

H Crítico vulnerabilidad

[CVE-2026-8927] When reusing a libcurl handle for sequential transfers driven by environment-variable proxy configur…

When reusing a libcurl handle for sequential transfers driven by environment-variable proxy configuration, libcurl fails to clear the proxy authentication state between requests. Specifically, if the initial transfer authenticates against `proxyA` using Digest auth, a subsequent transfer routed through `proxyB` erroneously leaks the `Proxy-Authorization:` header intended solely for `proxyA`.

H Alto vulnerabilidad

[CVE-2026-8932] libcurl would reuse a previously created connection even when some mTLS config related option had be…

libcurl would reuse a previously created connection even when some mTLS config related option had been changed that should have prohibited reuse. libcurl keeps previously used connections in a connection pool for subsequent transfers to reuse if one of them matches the setup. However, some TLS settings related to client certificates were left out from the configuration match checks, making them m…

H Crítico vulnerabilidad

[CVE-2026-9079] libcurl had a flaw that when instructed to clear proxy authentication credentials which made it not …

libcurl had a flaw that when instructed to clear proxy authentication credentials which made it not do so, leaving the old credentials around to get used for subsequent transfers that should not know nor use them.

H Alto vulnerabilidad

[CVE-2026-9080] Calling `curl_easy_pause()` within the event-based `CURLMOPT_SOCKETFUNCTION` callback triggers a use…

Calling `curl_easy_pause()` within the event-based `CURLMOPT_SOCKETFUNCTION` callback triggers a use-after-free vulnerability, where libcurl attempts to store a flag using a dangling struct pointer immediately after that pointer's memory has been freed.

H Alto vulnerabilidad

[CVE-2026-9545] In this scenario, libcurl first uses a proper HTTP/3 server for the initial transfers, and when it m…

In this scenario, libcurl first uses a proper HTTP/3 server for the initial transfers, and when it makes a second transfer to the same site it has been replaced by the attacker's impostor machine - without a valid certificate. When libcurl returns to the hostname the second time with a cached SSL session (`CURLOPT_SSL_SESSIONID_CACHE` is not disabled) and early data enabled (the `CURLSSLOPT_EARLY…

H Alto vulnerabilidad

[CVE-2026-9546] A vulnerability in libcurl caused the HTTP `Referer:` header to persist even when explicitly cleared…

A vulnerability in libcurl caused the HTTP `Referer:` header to persist even when explicitly cleared. While the documentation states that passing NULL to `CURLOPT_REFERER` suppresses the header, the option failed to clear the internal state. As a result the previous referrer string was erroneously reused and sent in subsequent requests, potentially leaking sensitive information to unintended serve…

📬 Alertas semanales SI directo en tu email

Las vulnerabilidades más críticas para LATAM, con contexto y recomendaciones accionables. Gratis.

Suscribirme →

H Alto vulnerabilidad

[CVE-2026-9547] When a libcurl-based application performs transfers via `SCP://` or `SFTP://` and utilizes the `CURL…

When a libcurl-based application performs transfers via `SCP://` or `SFTP://` and utilizes the `CURLOPT_SSH_KEYFUNCTION` callback, it may silently accept an untrusted server. This vulnerability occurs when a server presents a host key type that does not match the specific key type already recorded for that host in the `known_hosts` file. Instead of rejecting the mismatch, the callback mechanism fa…

H Alto vulnerabilidad

[CVE-2026-12064] When a user invokes curl using a schemeless URL combined with `--proto-default` sftp (or scp), a dis…

When a user invokes curl using a schemeless URL combined with `--proto-default` sftp (or scp), a disconnect occurs between the tool layer and libcurl. The tool layer incorrectly infers the URL scheme, which erroneously bypasses the initialization of critical SSH security options like CURLOPT_SSH_HOST_PUBLIC_KEY_SHA256 and CURLOPT_SSH_KNOWNHOSTS. Conversely, the libcurl runtime successfully honors …

H Alto vulnerabilidad

[CVE-2026-8286] A vulnerability exists where a new transfer that uses STARTTLS to upgrade the connection might reuse…

A vulnerability exists where a new transfer that uses STARTTLS to upgrade the connection might reuse an existing live connection even though the TLS configuration mismatches so it should not.

H Crítico vulnerabilidad

[CVE-2026-8924] A flaw in curl’s cookie parsing logic allows a malicious HTTP server to set 'super cookies' that byp…

A flaw in curl’s cookie parsing logic allows a malicious HTTP server to set 'super cookies' that bypass the Public Suffix List check. This enables an attacker-controlled origin to inject cookies that curl subsequently scopes and transmits to unrelated third-party domains.

H Crítico vulnerabilidad

[CVE-2026-8925] The curl logic that works with SASL authentication could end up cleaning up the GSASL context *twice…

The curl logic that works with SASL authentication could end up cleaning up the GSASL context *twice* without clearing the pointer in between, making it `free()` the same pointer twice.

H Crítico vulnerabilidad

[CVE-2026-10536] A use-after-free vulnerability exists in libcurl when an application configures an HTTP/2 stream-dep…

A use-after-free vulnerability exists in libcurl when an application configures an HTTP/2 stream-dependency tree via `CURLOPT_STREAM_DEPENDS` or `CURLOPT_STREAM_DEPENDS_E`, subsequently invokes `curl_easy_reset()`, and finally terminates the handle with `curl_easy_cleanup()`. During this final cleanup phase, libcurl attempts to access and modify an internal structure that was already freed during …

H Alto vulnerabilidad

[CVE-2026-11352] An issue in curl’s QUIC UDP receive function allows a malicious HTTP/3 server to trigger a remote de…

An issue in curl’s QUIC UDP receive function allows a malicious HTTP/3 server to trigger a remote denial of service against a curl or libcurl client. Because the helper function discards zero-length UDP datagrams before counting them toward the per-call packet budget, a connected QUIC peer can continuously stream empty datagrams to indefinitely stall the client.

H Crítico vulnerabilidad

[CVE-2026-11564] libcurl keeps previously used connections in a connection pool for subsequent transfers to reuse if …

libcurl keeps previously used connections in a connection pool for subsequent transfers to reuse if one of them matches the setup. An easy handle that first uses default native CA trust can continue trusting the native platform store after the application switches that same handle to custom CA material for a later transfer.

🛡 ¿Estás expuesto a alguna de estas vulnerabilidades?

Evaluación gratuita inicial con el equipo 2MCI: identifica exposición y plan de remediación.

Habla con un experto →

H Alto vulnerabilidad

[CVE-2026-11586] By default, curl automatically responds to WebSocket PING frames. Because curl lacks an upper bound …

By default, curl automatically responds to WebSocket PING frames. Because curl lacks an upper bound on memory allocation for unacknowledged frames, a malicious server can exhaust all available memory by flooding curl with rapid, sequential PING messages.

H Crítico vulnerabilidad

[CVE-2026-11856] Successfully using libcurl to do a transfer to a specific HTTP origin (`hostA`) with **Digest** auth…

Successfully using libcurl to do a transfer to a specific HTTP origin (`hostA`) with **Digest** authentication and then changing the origin to a different one (`hostB`) for a second transfer, reusing the same handle, makes libcurl wrongly pass on the `Authorization:` header field meant for `hostA`, to `hostB`.