PULSE
FEED
ransomqilin reclama a Meridian Capital Group · US · Financial Servicesransompixelleaks reclama a KDBS Solutions (client hosting) · Technologyransompixelleaks reclama a Proymoda (proymoda.com.mx) · MX · Retail & E-Commerceransomhelix reclama a Veritiv · US · Manufacturingransomvortex reclama a Drive Medical - 1,442,814 records · US · Healthcareransomhelix reclama a Sonoco · US · Manufacturingransomendzone reclama a West-Com Nurse Call Systems, Inc · US · Healthcareransomcurious worm reclama a examinetics.com · US · Healthcareransombraincipher reclama a intelligentaudit.com · US · Professional Servicesransombraincipher reclama a roedentallab.com · DE · Healthcareransombraincipher reclama a edi-uae.com · AE · Professional Servicesransombraincipher reclama a havingbabies.com · AU · Healthcareransomaoqin reclama a Esco Optics · US · Manufacturingransompayload reclama a WWGlas · DE · Manufacturingransomqilin reclama a Meridian Capital Group · US · Financial Servicesransompixelleaks reclama a KDBS Solutions (client hosting) · Technologyransompixelleaks reclama a Proymoda (proymoda.com.mx) · MX · Retail & E-Commerceransomhelix reclama a Veritiv · US · Manufacturingransomvortex reclama a Drive Medical - 1,442,814 records · US · Healthcareransomhelix reclama a Sonoco · US · Manufacturingransomendzone reclama a West-Com Nurse Call Systems, Inc · US · Healthcareransomcurious worm reclama a examinetics.com · US · Healthcareransombraincipher reclama a intelligentaudit.com · US · Professional Servicesransombraincipher reclama a roedentallab.com · DE · Healthcareransombraincipher reclama a edi-uae.com · AE · Professional Servicesransombraincipher reclama a havingbabies.com · AU · Healthcareransomaoqin reclama a Esco Optics · US · Manufacturingransompayload reclama a WWGlas · DE · Manufacturing
← Todos os CVEs
CVE Watch17 de nov. de 2026

CVE-2026-130626

The core JDK HTTP client (a2a-java-sdk-http-client) applies the GHSA-9rhm redirect-neutralization only to the POST path. JdkGetBuilder.get()

CVSS

7.5

Alta

EPSS

—

KEV

—

Exploit Today

—

0-100

Publicado: 17 de nov. de 2026 · Última mod.: 17 de nov. de 2026 · CWE-522

EPSS · 30d

Ainda não há histórico EPSS suficiente.

Descrição técnica

The core JDK HTTP client (a2a-java-sdk-http-client) applies the GHSA-9rhm redirect-neutralization only to the POST path. JdkGetBuilder.get(), JdkGetBuilder.getAsyncSSE(), and JdkDeleteBuilder.delete() call the injected httpClient directly, with no redirect gate. An application that supplies a redirect-capable HttpClient (Redirect.NORMAL/ALWAYS) — which is the SDK-documented way to enable POST redirects — silently follows cross-authority redirects on every credentialed GET/DELETE request. The JDK strips Authorization cross-origin, but forwards the four allowlisted custom credential headers (X-API-Key, API-Key, X-Auth-Token, X-Authentication) to the attacker-controlled authority. This is an incomplete-fix variant of GHSA-9rhm: the fix hardened the default client and added a POST-only two-step opt-in, but never covered GET/DELETE.

Referências oficiais
CVEs relacionados
CVECVSSEPSSKEVRExploitTítuloMod.
CVE-2026-126556—
—
———Invocation of Process Using Visible Sensitive Information, Insufficiently Protected Credentials vulnerability in Broadcom AutoSys Workload Automation (AutoSys engine (AE) native clients modules) on Windows, Linux allows Collect Data from Common Resource Locations.This issue affects AutoSys Workload Automation: 24.2.00-0210 and earlier (verified on 24.2.00-0210; earlier range unestablished), 24.2.01 (when the -pw/-pwx options are used).12h
CVE-2026-126550—
—
———Insertion of Sensitive Information into Log File, Insufficiently Protected Credentials vulnerability in Broadcom AutoSys Workload Automation (Workload Control Center (WCC) modules) on Windows, Linux allows Reusing Session IDs (Session Replay).This issue affects AutoSys Workload Automation: from 12.1.00 through 24.2.00.13h
CVE-2026-1306277.5 ALT
—
———The Vert.x HTTP client transport (a2a-java-sdk-http-client-vertx) hand-rolls a POST redirect follower that, when the documented PostBuilder.followRedirects(true) opt-in is enabled, re-issues the redirected request with the full request header map copied verbatim and performs no credential stripping and no same-authority check. A malicious, compromised, or mistyped agent that returns a 30x response with an absolute cross-host Location causes the client to forward the standard Authorization header (Bearer/Basic/OAuth) — plus every other header, including the allowlisted API-key headers — to the attacker-controlled authority. This breaks the project's own cross-transport invariant (SECURITY.md §8, OkHttpPostRedirectHeaderLeakTest) that credentials are stripped on cross-authority redirects even when redirects are followed. The sibling JDK and OkHttp/Android transports strip Authorization; Vert.x uniquely does not. This is a "fix introduced the bug" variant — the follower was added by the GHSA-9rhm hardening PR (3ae82912, refined by a5e76a0b).11h
CVE-2026-76823—
—
——0OpenCTI is an open source platform for managing cyber threat intelligence knowledge and observables. Prior to 7.260706.0, the logsWorkerConfig GraphQL query is authorized with the broad CONNECTORAPI capability and returns Elasticsearch connection details including elasticsearch_username, elasticsearch_password, elasticsearch_api_key, the URL, index, proxy, and TLS-verification setting. A holder of any connector API bearer token can retrieve this credential material. If the returned credentials are valid and Elasticsearch is reachable, the caller can directly read, modify, or delete OpenCTI indices and audit history outside application-layer role, marking, organization, and audit controls, with the practical impact bounded by the credentials' privileges and network reachability. This issue is fixed in version 7.260706.0.8h
CVE-2026-1155637.5 ALT
—
——0The Model Context Protocol Python SDK is the official Python SDK for Model Context Protocol servers and clients. From 1.9.1 until 1.30.0 and 2.2.0, OAuth client support in mcp.client.auth can send credentials to an authorization server chosen by an untrusted MCP server. ClientCredentialsOAuthProvider and PrivateKeyJWTOAuthProvider cannot identify the authorization server that owns their credentials. Affected HTTP clients using those providers, OAuthClientProvider, or the deprecated 1.x RFC7523OAuthClientProvider can disclose a client_secret, authorization code, PKCE code_verifier, or signed client assertion. MCP servers, stdio clients, and clients that attach their own tokens or headers are not affected. Interactive OAuthClientProvider use requires a person to start sign-in, while the unattended providers do not. For ClientCredentialsOAuthProvider and PrivateKeyJWTOAuthProvider, callers must configure issuer= after upgrading because omission still follows the MCP server's advertised authorization server, and the deprecated RFC7523OAuthClientProvider must be replaced because it has no issuer option. A stored client registration without an issuer remains unbound after upgrading, so stored OAuth client information must be cleared once to register again or a manually pre-registered record must be updated with its issuer. This issue is fixed in versions 1.30.0 and 2.2.0.1d
CVE-2026-1042535.2 MÉD
—
——0OpenCTI is an open source platform for managing cyber threat intelligence knowledge and observables. Prior to 7.260715.0, a ProfileQuery response can expose the user's TOTP MFA secret after activation. A person who can access the profile response can recover the secret, enroll a duplicate authenticator, and generate valid one-time codes, undermining the account's second-factor protection. This issue is fixed in version 7.260715.0.8h