Apache Pinot before 1.6.0 can read unauthorized tables (CVE-2026-73322)
With broker access control on, lookup() can name a dimension table that the FROM-clause check never authorizes.
With broker access control on, lookup() can name a dimension table that the FROM-clause check never authorizes.
Caller-supplied orderBy, sortOrder and related parameters are concatenated on Center and datatable read APIs.
The flaw is in outStandingAmountPercentageCondition on the advanced search HTTP endpoint through version 1.15.0.
The authors say Apache Struts2 JSON Plugin changes through S2-072 still do not stop maximised comma-array consumption.
Daniel Owens cites earlier Struts2 JSON denial-of-service write-ups and a naïve proof-of-concept script; this excerpt ends before new details.
Apache rates the stack read overflow low and says only non-RFC9525 wildcard certificates trigger it; 0.41.1 fixes it.
Apache calls the flaw important: peers can send regular AMQP frames that Proton dispatches as SASL, with no username set.
Deeply nested message bodies decoded by pn_message_body() can overflow the stack; 0.41.1 fixes PROTON-2976.
pn_ssl_domain_set_trusted_ca_db() and pn_tls_config_set_trusted_certs() add CAs instead of replacing system anchors.
A record timestamp near Long.MAX_VALUE can overflow the next punctuation time and stall a StreamThread.
Apache calls the flaw important: a small input can declare a huge size and force a large allocation.
Flexible-protocol readers keep a RawTaggedField per unknown field, with the count limited only by the request frame.
Only the compressed size is checked against telemetry.max.bytes, default 1 MB, before an unbounded decompress.
Code-generated readers size arrays from a sender-declared count checked only against remaining buffer bytes.
DefaultJwtValidator verifies signatures only if sasl.oauthbearer.jwks.endpoint.url is set; that setting is unset by default.
The bundled JWKS validator always checks the signature, but iss and audience checks need explicit settings.
Authenticated clients with CLUSTER_ACTION can terminate the controller using an empty-topics FetchSnapshotRequest.
Saxon needs 4.18.5, 4.22.2, or 4.23.0; stopping at the XPath and Smooks fix 4.22.1 misses it.
SSHRemoteJobOperator quotes templated environment values only once inside an already-quoted wrapper, so $(...) runs remotely.
Eight critical and high issues span Camel K and Camel components, with fixes that differ by branch.
JFrog showed crashes, memory corruption, and an endless loop; a full FFmpeg remote code execution exploit was not shown.
An oss-security forward of Apache's October 20 note names CVE-2026-111813, but this excerpt omits each flaw's impact.
Every Vysper version lacks an XEP-0077 authentication check; Apache rates it important at CVSS 8.8 and unsupported when assigned.
CVE-2026-115721 is an unauthenticated network denial of service scored CVSS 7.5; the retired project will not be fixed.
Unmuted consumer exceptions in camel-coap can expose sensitive information to unauthenticated remote users; CVSS is 5.3.
A low-privileged attacker can inject expressions through the CamelAwsS3Key header; the CVSS score is 5.4.
Cached introspection results are not limited by token expiry, so expired access tokens can still be accepted.
A low-privileged caller can steer conversion output to an arbitrary directory through an unvalidated header.
Path checks added after CVE-2026-40047 do not reject absolute paths supplied as custom CLI arguments.
camel-oauth from 4.19.0 before 4.22.2 can reuse client-credentials bearer tokens; CVSS 3.1 is 4.8.
camel-saxon before 4.18.5 and before 4.22.2 parses Source bodies with Saxon defaults; CVSS is 7.5.
All Apache Abdera versions are affected and unsupported; CVSS 4.0 is 8.7 with high confidentiality impact.
Critical scores are third-party library ratings; Atlassian says its product risk is lower and not immediately critical.
Fixed PHP builds are 8.5.12, 8.4.27, 8.3.36, and 8.2.35; LiteLLM 1.107.0 stole secrets, so pin 1.106.2 and rotate them.
The Apache Pulsar PMC says the end-of-life manager lacks authentication and authorization and can expose Pulsar admin credentials.
The Pulsar PMC posted a combined advisory, but the excerpt omits the individual CVE ids and affected ranges.
Apache rates the legacy pipe sendFile flaw important; the notice gives no versions or fix.
Versions 2.0.0 before 2.0.11 run load and delete operations with a hardcoded root identity.
The oss-security note rates the flaw important and does not list versions or a fix.
Versions from 1.3.3 before 2.0.11 can exhaust memory via BigDecimal toPlainString.
Entities are extracted by the model from each article. First seen , last mentioned . Watching keeps it in this browser only (no account); the watchlist page and dashboard alerts use it.
Today 360 readers · 389 views · 299 reads · all time 158K views