Latest
Most recently published vulnerabilities
RoutineCVE-2026-132665enterprisedb · postgres enterprise managerenterprisedb postgres enterprise managerIn Postgres Enterprise Manager (PEM), the pem.deploy_job_template() function does not check that the caller can access the servers, groups and agents it deploys a job template to. When PEM teams are used to separate access, a user with the scheduled tasks role (pem_manage_schedule_task) can deploy and schedule SQL or shell job steps on agents that belong to other teams.
From PEM 10.6.1, PEM checks team access for every server, group and agent a template is deployed to.CVSS5.8MediumRoutineCVE-2026-132664enterprisedb · postgres enterprise managerenterprisedb postgres enterprise managerIn Postgres Enterprise Manager (PEM), any PEM user can read the encrypted passwords that PEM agents use to connect to monitored servers, including the PEM backend superuser password stored when the PEM server is configured. Unless a custom encryption key is configured, these passwords are encrypted with a key that is the same in every PEM installation, so they can be decrypted.
From PEM 10.6.1, PEM users can no longer read these passwords.CVSS7.0HighRoutineCVE-2026-132663enterprisedb · postgres enterprise managerenterprisedb postgres enterprise managerIn Postgres Enterprise Manager (PEM), webhook URLs are not validated, and the PEM agent does not restrict the URL schemes it uses to deliver webhooks. A user with the alert configuration role (pem_config_alert) can set up a webhook with a file:// URL. When the webhook is sent, the agent on the PEM server, which runs as root by default, reads the local file and stores its contents in the webhook error record in the PEM database, where any PEM user can read it.
From PEM 10.6.1, PEM accepts and sends only http and https webhook URLs.CVSS7.1HighRoutineCVE-2026-132662enterprisedb · postgres enterprise managerenterprisedb postgres enterprise managerIn Postgres Enterprise Manager (PEM), the SQL Profiler save and load functions in the PEM web application do not keep the client-supplied file name inside the user's storage directory. A user with the SQL Profiler role (pem_comp_sqlprofiler) can read JSON files, and overwrite files that the PEM web server account can write, outside their own storage directory. Overwriting the PEM web application's configuration database stops the web console for all users.
From PEM 10.6.1, the SQL Profiler only reads and writes files inside the user's storage directory.CVSS7.2HighRoutineCVE-2026-132661enterprisedb · postgres enterprise managerenterprisedb postgres enterprise managerIn Postgres Enterprise Manager (PEM), multi-factor authentication (MFA) is not enforced on the PEM web application's own routes. An attacker who knows the password of a user who has enrolled a second factor can skip the second factor and call PEM's pages and APIs directly, with that user's permissions. A similar issue in pgAdmin 4 was assigned CVE-2024-4215.
From PEM 10.6.1, every authenticated PEM route requires a completed MFA check.CVSS7.6HighPrioritiseCVE-2026-132660enterprisedb · postgres enterprise managerenterprisedb postgres enterprise managerIn Postgres Enterprise Manager (PEM), several SECURITY DEFINER functions in the pem schema of the PEM backend database are owned by a superuser but do not set a safe search_path. Any PEM user who can connect to the PEM backend database can create objects that these functions use in place of the intended ones, and so run arbitrary SQL with superuser privileges. Temporary objects can be used for this on every supported PostgreSQL version, and objects in the public schema on PostgreSQL 14 backends and backends upgraded from PostgreSQL 14.
From PEM 10.6.1, these functions run with a fixed search_path.CVSS9.4CriticalPrioritiseCVE-2026-132659enterprisedb · postgres enterprise managerenterprisedb postgres enterprise managerIn Postgres Enterprise Manager (PEM), the row-level security policies on pem.job and pem.jobstep that apply to PEM agents do not limit an agent to its own jobs. An attacker who controls one monitored host, and so its PEM agent certificate, can create, change or delete jobs for every other agent, including the agent on the PEM server. Agents run SQL job steps with the database credentials of the server they monitor, and shell job steps where batch jobs are enabled, so compromising one monitored host can give superuser SQL access to every monitored database and to the PEM backend.
From PEM 10.6.1, PEM agents can no longer create jobs or change job definitions or job steps.CVSS9.4CriticalPrioritiseCVE-2026-132658enterprisedb · postgres enterprise managerenterprisedb postgres enterprise managerIn Postgres Enterprise Manager (PEM), the pem_agent role, which every PEM agent login inherits, is a member of the PostgreSQL pg_read_server_files and pg_write_server_files roles on the PEM backend database. An attacker who controls any monitored host, and so its PEM agent certificate, can read and write files on the PEM server host as the postgres operating system user. This includes the PEM certificate authority key, which lets the attacker issue certificates for other agents and act as them.
From PEM 10.6.1, PEM agents no longer hold these roles.CVSS9.4CriticalPrioritiseCVE-2026-126054google cloud · bigquery studio +2 morePath Traversal in Dataform, BigQuery Studio and Colab Enterprise allows Cross-Tenant File Read and WriteA Path Traversal vulnerability in workspace directory handling and Git integration in Google Cloud Dataform, BigQuery Studio and Colab Enterprise on Google Cloud Platform allows an authenticated remote attacker to read private files and create arbitrary files across tenant repositories using crafted workspace operations and Git integration requests.
This vulnerability was patched on 10 October 2026, and no customer action is needed.CVSS9.3CriticalRoutineRUSTSEC-2026-0587Crates.Io · wasmtime-wasiCrates.Io wasmtime-wasiWASI filesystem sandbox escape on Windows through a drive-prefixed path component
This is an entry in the RustSec database for the Wasmtime security advisory
located at
https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-f2pq-268w-886c
For more information see the GitHub-hosted security advisory.CVSSUnscoredRoutineRUSTSEC-2026-0584Crates.Io · tokio-rate-limitCrates.Io tokio-rate-limitgRPC `IpKeyExtractor` keys on client-supplied forwarding headers
`tonic_middleware::IpKeyExtractor` is documented as rate limiting gRPC requests by client IP address,
but on a standard tonic server it keys on client-supplied `x-forwarded-for` and `x-real-ip`
headers. In 0.5.0–0.9.1, the extractor reads those headers directly; in 0.10.0–0.11.0, it first
checks for a bare `std::net::SocketAddr` request extension—which `tonic::transport::Server` never
supplies, as it provides `TcpConnectInfo` instead—and falls back to the same headers. Direct
clients can therefore choose their rate-limit key to bypass per-IP rate limits and increase the
number of tracked keys; without forwarding headers, 0.5.0–0.9.1 allow requests without limiting
them and 0.10.0–0.11.0 reject them by default unless `.fail_open()` is enabled.
Applications are affected if they use `GrpcRateLimitLayer` with `IpKeyExtractor` (the
`tonic-support` feature). The HTTP middleware's `IpKeyExtractor` reads `ConnectInfo<SocketAddr>` and
is not affected.
Version 0.11.1 fixes `IpKeyExtractor` to honor a server-supplied `SocketAddr` override first and then
read the TCP peer address from tonic's `TcpConnectInfo` (which `tonic::transport::Server` attaches
to plaintext connections and connections using its built-in TLS), without ever reading forwarding
headers. Deployments behind a trusted proxy can use the new opt-in `ForwardedIpKeyExtractor`, which
reads a single configured header (`x-forwarded-for` or `x-real-ip`) and is only correct when that
proxy sets the header as documented.
If you cannot upgrade to 0.11.1, use a custom key extractor that reads the peer IP from tonic's
connection information for the transport in use (including TLS) and rejects requests without a
verified peer address before invoking the limiter, or restrict backend access to a trusted proxy
that strips all incoming `x-forwarded-for` and `x-real-ip` fields and sets one `x-forwarded-for`
value to the verified client IP on every request.CVSSUnscoredInsufficient evidenceRUSTSEC-2026-0585Crates.Io · pqcrypto-mlkemCrates.Io pqcrypto-mlkemML-KEM does not perform the FIPS 203 input checks
`pqcrypto-mlkem` wraps PQClean's ML-KEM implementation, which does not perform
the input checks required by FIPS 203:
- encapsulation does not perform the encapsulation key modulus check
(section 7.2), so encapsulation keys with coefficients that are not reduced
modulo q are accepted;
- decapsulation does not perform the decapsulation key hash check
(section 7.3), so a decapsulation key whose stored hash or embedded
encapsulation key has been altered is accepted.
With the Wycheproof ML-KEM vectors, 108 / 112 / 116 invalid encapsulation keys
(ML-KEM-512 / -768 / -1024) and 2 invalid decapsulation keys per parameter set
are accepted.
This does not disclose key material. It is a FIPS 203 non-conformance, and an
affected implementation can disagree with a conforming one about which keys
are valid.
The crate is unmaintained (see RUSTSEC-2026-0161) and no patched version is
expected. Migrating to a maintained implementation, such as the
[`ml-kem`](https://crates.io/crates/ml-kem) crate, is recommended.CVSSUnscoredInsufficient evidenceRUSTSEC-2026-0586Crates.Io · pqcrypto-mldsaCrates.Io pqcrypto-mldsaML-DSA verification accepts non-conforming signatures with the `avx2` feature
With the default `avx2` feature on x86_64 (non-Windows) and a CPU that supports
AVX2, `pqcrypto-mldsa` verifies signatures with PQClean's AVX2 implementation of
ML-DSA. That implementation predates two upstream fixes
([pq-crystals/dilithium#113](https://github.com/pq-crystals/dilithium/issues/113),
3 June 2026):
- the verifier does not check that the infinity norm of `z` is below
`γ1 − β` (FIPS 204, Algorithm 8, line 13), so it accepts signatures that
conforming verifiers reject;
- `use_hint_avx()` mishandles a boundary case, so one class of valid
signatures is rejected.
Creating an accepted out-of-bound signature requires the private key. The
practical effect is that verification results differ between this crate with
AVX2 and conforming implementations, including this crate without AVX2.
The Wycheproof ML-DSA verification vectors reproduce both defects: with AVX2,
37 / 41 / 49 invalid vectors (ML-DSA-44 / -65 / -87) are accepted and one valid
vector per parameter set is rejected.
The crate is unmaintained (see RUSTSEC-2026-0166) and no patched version is
expected. Disabling the `avx2` feature avoids the affected code. Migrating to a
maintained implementation, such as the [`ml-dsa`](https://crates.io/crates/ml-dsa)
crate, is recommended.CVSSUnscoredRoutineRUSTSEC-2026-0583Crates.Io · sad-rsaCrates.Io sad-rsaPanics during RSA private-key construction, validation, or re-encoding
`RsaPrivateKey` private-key construction, validation, and serialization can panic across three
classes of inputs, as well as when re-encoding certain valid keys:
- `RsaPrivateKey::from_components` and PKCS#1 or PKCS#8 private-key decoding (DER or PEM) can panic
during validation when a supplied factor equals 1, because `RsaPrivateKey::validate()` let a
factor of 1 reach a later check that panicked.
- `RsaPrivateKey::from_primes` and `RsaPrivateKey::from_p_q` can panic during construction when a
supplied factor is 0, 1, or even.
- Prime recovery in `RsaPrivateKey::from_components` can panic when the private exponent is 0.
- For a key, including a valid one, whose first prime occupies more limbs than the second,
`crt_coefficient`, `to_pkcs1_der`, `to_pkcs8_der`, and `serde` serialization can panic.
An application that imports untrusted private keys or factors, or re-encodes such keys, can lose a
worker, or the whole process when built with `panic = "abort"`. Public-key parsing is not affected.
Fixed in 0.10.4, which rejects factors below 2, even factors, repeated factors, and a zero private
exponent during prime recovery, and computes the CRT coefficient and re-encodes valid two-prime
keys when the first prime occupies more limbs than the second.
If you cannot upgrade to 0.10.4, isolate the entire import, construction, CRT calculation, or
serialization in a separate process and treat an abnormal exit as an operation failure, or use
`catch_unwind` around the entire operation when panics unwind.CVSSUnscoredRoutineCVE-2026-133608openzipkin · zipkinOpenZipkin HTTP Collector ZipkinHttpCollector.java UnzippingBytesRequestConverter.convertRequest data amplificationA vulnerability was identified in OpenZipkin Zipkin 3.6.1. This affects the function UnzippingBytesRequestConverter.convertRequest of the file zipkin-server/src/main/java/zipkin2/server/internal/ZipkinHttpCollector.java of the component HTTP Collector. Such manipulation leads to highly compressed data. The attack can be executed remotely. The pull request to fix this issue awaits acceptance.CVSS6.9MediumRoutineCVE-2026-129424solidres.com · solidres extension for joomlaJoomla Extension - solidres.com - Unauthenticated stored XSS through guest reservation details in Solidres extension 1.0.0-3.4.1, 4.0.0-4.6.0The customer details layout of the administrator reservation view printed guest-supplied booking details, including the email and phone number inside mailto: and tel: links, without escaping, allowing unauthenticated guests to inject HTML attributes and script. Sites using the Custom Fields, Hub or Experience add-ons also need to update them to Custom Fields 2.0.3, Hub 2.5.0 and Experience 2.5.0.CVSS8.7HighPrioritiseCVE-2026-129073miniorange · miniorange otp verificationWordPress miniorange otp verification plugin <= 5.6.1 - Broken Authentication vulnerabilityAuthentication Bypass Using an Alternate Path or Channel vulnerability in miniOrange miniorange otp verification miniorange-otp-verification allows Authentication Abuse.This issue affects miniorange otp verification: from n/a through 5.6.1.CVSS9.8CriticalPrioritiseCVE-2026-128997romancode · mapsvgWordPress MapSVG plugin <= 9.0.5 - Broken Access Control vulnerabilityMissing Authorization vulnerability in RomanCode MapSVG mapsvg-lite-interactive-vector-maps allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects MapSVG: from n/a through 9.0.5.CVSS7.5HighRoutineCVE-2026-109878elementor · elementor website builderWordPress Elementor Website Builder plugin <= 4.4.0 - Cross Site Scripting (XSS) vulnerabilityImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Elementor Elementor Website Builder elementor allows Reflected XSS.This issue affects Elementor Website Builder: from n/a through 4.4.0.CVSS7.1HighPrioritiseCVE-2026-80188buddyboss · buddyboss addonsBuddyBoss Addons <= 1.2.1 - Unauthenticated Account Takeover via Unverified Social Login Identity TokensThe BuddyBoss Addons plugin for WordPress is vulnerable to Authentication Bypass leading to Account Takeover in versions up to, and including, 1.2.1. This is due to the Social Login REST endpoint trusting unverified Apple and Facebook identity-token claims and linking an attacker-controlled provider identifier to an existing WordPress user selected by the token’s email claim. This makes it possible for unauthenticated attackers who know a user’s email address to associate their provider identity with that account, including administrator accounts, and subsequently authenticate as the victim. Successful exploitation requires the BuddyBoss Platform plugin to be installed and active, with the Social Login module and selected provider enabled and configured. On sites with the separate BuddyBoss App JWT component, the vulnerable REST request can return an application token immediately.CVSS9.8Critical