CVE-2026-69435
Missing authorization in Azure SRE Agent allows an authorized attacker to elevate privileges over a network.
CVSS
9.6
Crítica
EPSS
0.6%
p47
KEV
—
Exploit Today
14
0-100
Publicado: 8 de out. de 2026 · Última mod.: 15 de out. de 2026 · CWE-918
0.4%EPSS · 30 dias0.6%
2026-10-092026-11-05
Missing authorization in Azure SRE Agent allows an authorized attacker to elevate privileges over a network.
CVECVSSEPSSKEVRExploitTítuloMod.
CVE-2026-76171——
———In Apache James server prior version 3.9.1 improper validation in JMAP webPush SSRF validation did lead to the possibility to reach internal addresses.
Users are recommended to upgrade to version 3.9.1 which fixes this issue.3hCVE-2026-1233105.4 MÉD—
———In JetBrains IntelliJ IDEA before 2026.3 kotlin scripts could trigger dependency downloads from arbitrary repositories in untrusted projects4hCVE-2026-1233076.8 MÉD—
———In JetBrains IntelliJ IDEA before 2026.3,
2026.2.4 unauthenticated connection to an arbitrary host via run configurations was possible4hCVE-2026-1194337.7 ALT—
———A server-side request forgery (SSRF) vulnerability exists in an undocumented API endpoint of Foxit Workspace due to insufficient validation of user-supplied URL and network parameters. A remote attacker could exploit this issue to induce the server to send requests to arbitrary internal or external resources, potentially enabling unauthorized access to internal services, network reconnaissance, and sensitive information disclosure.10hCVE-2026-1194317.7 ALT—
———A server-side request forgery (SSRF) vulnerability exists in Foxit Workspace's file-upload functionality. Insufficient validation of user-supplied links may allow a remote attacker to induce the server to access internal resources and return their contents, potentially resulting in sensitive information disclosure and unauthorized access to internal services.10hCVE-2026-889818.6 ALT—
———Kubeflow Pipelines enables users to build and deploy portable, scalable machine learning workflows. Prior to 2.18.0, the frontend artifact download path for source=s3 or source=minio accepts providerInfo.Params.endpoint, and the archived pod-log path accepts S3-compatible endpoint metadata from workflow status, without requiring those endpoints to match operator-controlled storage configuration. In the shipped authorization-disabled standalone configuration, an unauthenticated caller can make the shared ml-pipeline-ui pod connect to arbitrary reachable hosts and return response data; requests may also reveal an access-key identifier when signed with configured object-store credentials. Multi-user secret-backed metadata remains restricted to the server namespace. This issue is fixed in version 2.18.0.16h