PULSE
FEED
ransomn0n reclama a Company #111 · AEransomeverest reclama a OR Technology · Technologyransomeverest reclama a Burris & MacOmber · Professional Servicesransomeverest reclama a Energy Storage Terminal in Singapore · SG · Energy & Utilitiesransomeverest reclama a Point Robotics · Technologyransomeverest reclama a Natuzzi · IT · Manufacturingransomeverest reclama a TECNA ICE · IT · Manufacturingransomeverest reclama a MediSolution · Healthcareransomeverest reclama a SleepEx LabRetriever · Healthcareransomcrypto24 reclama a Antah HealthCare Group · MY · Healthcareransomcrypto24 reclama a DATEM, Inc. · PH · Technologyransomwhitearmor reclama a gamblinglore · Retail & E-Commerceransomwhitearmor reclama a Verification · Technologyransomulose reclama a zzq-testransomn0n reclama a Company #111 · AEransomeverest reclama a OR Technology · Technologyransomeverest reclama a Burris & MacOmber · Professional Servicesransomeverest reclama a Energy Storage Terminal in Singapore · SG · Energy & Utilitiesransomeverest reclama a Point Robotics · Technologyransomeverest reclama a Natuzzi · IT · Manufacturingransomeverest reclama a TECNA ICE · IT · Manufacturingransomeverest reclama a MediSolution · Healthcareransomeverest reclama a SleepEx LabRetriever · Healthcareransomcrypto24 reclama a Antah HealthCare Group · MY · Healthcareransomcrypto24 reclama a DATEM, Inc. · PH · Technologyransomwhitearmor reclama a gamblinglore · Retail & E-Commerceransomwhitearmor reclama a Verification · Technologyransomulose reclama a zzq-test
← All CVEs
CVE WatchOct 26, 2026

CVE-2026-32998

This vulnerability in Veeam Service Provider Console allows for remote code execution.

CVSS

—

No CVSS

EPSS

0.5%

p44

KEV

—

Exploit Today

13

0-100

Published: May 28, 2026 · Last modified: Oct 26, 2026 · CWE-233

EPSS · 30d
0.5%EPSS · 30 days0.6%
2026-09-282026-10-26
Technical description

This vulnerability in Veeam Service Provider Console allows for remote code execution.

Official references
Related CVEs
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2026-55835—
33.4%
——10Lookyloo is a web interface that allows users to capture a website page and then display a tree of domains that call each other. Prior to version 1.39.4, an unauthenticated user can trigger Lookyloo's "report a capture" email on demand (this is expected). The /json/<uuid>/report API endpoint (CaptureReport) is incorrectly passing the email and comment parameters, overwriting as_admin. When True, as_admin will trigger a search query on a MISP instance (if configured) and add a list of matching URLs in the email sent to the analyst (not the submitter, so there is no risk of leaking information) . It could potentially cause a DoS on the MISP instance. This issue has been patched in version 1.39.4.4d
CVE-2026-05156.2 MED
4.1%
——1Insufficient Parameter Validation in the SchedGet() system call could allow an attacker with local access to cause a crash of the QNX Neutrino kernel.104d
CVE-2026-335853.8 LOW
2.9%
——1Improper management of the idle timeout parameter in the Keycloak interface of the Arqit SKA-Platform enables an attacker to impersonate an authenticated tenant user via an unexpired browser session. This issue affects Symmetric Key Agreement Platform: before 26.03.20h
CVE-2018-252336.2 MED
10.5%
——3WebDrive 18.00.5057 contains a denial of service vulnerability that allows local attackers to crash the application by supplying an excessively long string in the username field during Secure WebDAV connection setup. Attackers can input a buffer-overflow payload of 5000 bytes in the username parameter and trigger a connection test to cause the application to crash.20d
CVE-2026-23708.1 HIG
38.8%
——12GitLab has remediated an issue in GitLab CE/EE affecting all versions from 14.3 before 18.8.7, 18.9 before 18.9.3, and 18.10 before 18.10.1 affecting Jira Connect installations that could have allowed an authenticated user with minimal workspace permissions to obtain installation credentials and impersonate the GitLab app due to improper authorization checks.104d
CVE-2025-550807.1 HIG
3.2%
——1In Eclipse ThreadX before 6.4.3, when memory protection is enabled, syscall parameters verification wasn't enough, allowing an attacker to obtain an arbitrary memory read/write.19d