Search: cert-pl.pl
112 threats
Most recently published first
| Severity | CVSS | Signals | Threat | Source | Published | Score and star |
|---|---|---|---|---|---|---|
| High | – | HighCERT/CCCVE-2026-96679 Bisheng, an open-source LLM application DevOps platform, contains three vulnerabilities: a legacy SSO endpoint that allows unauthenticated account takeover and administrative access; an IDOR vulnerability exposing cross-user workflow data to authenticated users; and a missing access control in the assistant service enabling credential abuse and data disclosure prior to version 2.5.0. Two of these vulnerabilities have been patched in versions 2.5.0 and 3.0.0 respectively, while the legacy SSO bypass remains unpatched. Manual mitigations are recommended until an official fix is available. | CERT/CC | |||
| High | 7.5 | EPSS 1.8% | High7.5EPSS 1.8%GCVE DatabaseCVE-2024-34459 CVE-2024-34459 affects the cert-manager Operator for Red Hat OpenShift, which extends Kubernetes by managing certificate authorities and certificates as first-class resources. The vulnerability involves improper certificate validation due to an oversized Subject Alternative Name (SAN) field, causing fallback to the Common Name (CN) field. This flaw could allow a remote attacker with a man-in-the-middle position and a trusted certificate matching the CN to bypass proper certificate validation, potentially enabling spoofing or interception of communications. The issue impacts TLS clients using GnuTLS on affected Red Hat products but does not affect TLS servers or clients using other cryptographic libraries such as OpenSSL. Red Hat has released version 1.17.2 of the cert-manager Operator to address this vulnerability. Automatic upgrade policies will apply the fix without user intervention; manual approval is required if the upgrade policy is set to manual. | GCVE Database | ||
| High | 8.1 | EPSS 0.6% | High8.1EPSS 0.6%CERT/CCCVE-2026-104937 Shopware 6.7 contains a stored cross-site scripting (XSS) vulnerability in its media upload functionality that allows attackers with upload access to execute arbitrary JavaScript in an administrator's browser. This can lead to theft of administrator authentication tokens and unauthorized access to the Shopware Administration API. If the compromised administrator has extension management privileges, attackers can upload and activate malicious plugins to achieve remote code execution on the server. No vendor patch or statement is currently available. Mitigation involves restricting media upload access to trusted users or disabling HTML file uploads. | CERT/CC | ||
| Low | 2.5 | EPSS 0.3% | Low2.5EPSS 0.3%GCVE DatabaseCVE-2025-6170 CVE-2025-6170 is a vulnerability in the interactive shell of the xmllint command-line tool used in Red Hat's cert-manager Operator for OpenShift. The flaw is a stack-based buffer overflow caused by improper input size checking of overly long commands, which can lead to a crash. Exploitation requires local access and manual interaction with the tool, making it unlikely in typical environments. The impact is limited to availability with no confidentiality or integrity loss. Red Hat rates this vulnerability as low severity due to its limited attack surface and specific usage scenario. No patch is currently available, but an upstream fix is recommended once released. Users with automatic update policies will receive the upgrade automatically; manual approval is required otherwise. | GCVE Database | ||
| High | – | EPSS 0.6% | HighEPSS 0.6%CERT/CCCVE-2026-103521 Thelia versions 2.6.0 and 2.6.1 contain multiple vulnerabilities affecting file management, Smarty templating, module installation, and administrative workflows. These include remote code execution, server-side template injection, stored and reflected cross-site scripting, open redirect, and username enumeration. Exploitation requires authenticated administrative access for most issues, but some vulnerabilities enable unauthenticated attackers to enumerate valid admin usernames. No patch is currently available, and risk mitigation involves restricting administrative interface access and disabling or limiting certain features. | CERT/CC | ||
| High | 8.8 | EPSS 0.3% | CVE-2026-1078130xJacky nginx-ui · Missing Authorization High8.8EPSS 0.3%CVE Database V5CVE-2026-107813 ## Summary Incomplete fix of GHSA-5v7c-xpfp-p65m: the secure-session (OTP step-up) requirement added to the nginx, cert, dns, backup, site, and stream mutation routers was not applied to the parallel api/cluster router, so cluster node management and cluster-wide nginx reload/restart run with only a JWT and no step-up. An authenticated user whose JWT is stolen or persisted, but who does not hold a fresh secure-session, can perform cluster node CRUD (including reading and rewriting a node token secret) and trigger cluster-wide nginx reload/restart. Confirmed at HEAD 2cb7ee9102c9d87274de2fa104db804841d140a0. ## The defect GHSA-5v7c-xpfp-p65m required a fresh secure session (an OTP step-up beyond the JWT) for sensitive mutation routes. The fix wrapped the nginx, cert, dns, backup, site, and stream mutation handlers in middleware.RequireSecureSession() and added reload/restart to the MCP sensitive-tool list. It did not touch the physically separate api/cluster package, whose router registers the same class of sensitive operations on the bare authenticated group. The fixed sibling, api/nginx/router.go: ```go o := r.Group("", middleware.RequireSecureSession()) // line 28 { o.POST("nginx/reload", Reload) // line 30 o.POST("nginx/restart", Restart) // line 31 } ``` The missed router, api/cluster/router.go, registers every sensitive operation directly on r with no RequireSecureSession wrapper: ```go nodeGroup := r.Group("nodes") // line 9, no step-up { nodeGroup.POST("", AddNode) // line 12 nodeGroup.POST("/:id", EditNode) // line 13 nodeGroup.DELETE("/:id", DeleteNode) // line 14 } r.POST("nodes/reload_nginx", ReloadNginx) // line 17 r.POST("nodes/restart_nginx", RestartNginx) // line 18 r.POST("namespaces", AddNamespace) // line 22 r.POST("namespaces/:id", ModifyNamespace) // line 23 r.DELETE("namespaces/:id", DeleteNamespace) // line 24 ``` Both routers mount on the same group in router/routers.go: `g := root.Group("/", middleware.AuthRequired(), middleware.Proxy())` (line 87); nginx.InitRouter(g) creates its own RequireSecureSession subgroup, cluster.InitRouter(g) does not. So the cluster routes inherit only AuthRequired and Proxy, exactly the pre-fix posture the advisory closed for the nginx routes. AuthRequired has no role gate, so any authenticated user reaches them. ## Attacker model and impact An authenticated, OTP-enabled user who does not present a fresh X-Secure-Session-ID (the parent advisory's model: a stolen or persisted JWT used without the step-up). Such a user can: add/edit/delete cluster nodes (AddNode/EditNode store an AES-serialized node token, the secret used to control a remote node, so this reads back and rewrites a cross-node credential); trigger nodes/reload_nginx and nodes/restart_nginx across the cluster (the exact reload/restart action class the fix protected on the single-node path); and add/modify/delete/reorder namespaces. Proof of concept: with a valid JWT but no fresh secure session, call POST /api/nodes (AddNode) or POST /api/nodes/reload_nginx. The nginx equivalent POST /api/nginx/reload returns the secure-session challenge; the cluster route succeeds. ## Verification Source-verified at HEAD: the nginx router wraps reload/restart in RequireSecureSession, the cluster router registers node/namespace/reload/restart directly on the group with no such wrapper, and both mount on the AuthRequired+Proxy-only group. I did not stand up a live nginx-ui. ## Suggested fix Wrap the cluster router's mutation handlers (node CRUD, nodes/reload_nginx, nodes/restart_nginx, namespace CRUD) in middleware.RequireSecureSession(), mirroring api/nginx/router.go. Secondary lower-confidence items worth checking in the same pass: the system/restart handler, the core-upgrade websocket, and the upstream socket PUT also appear to run without the step-up (I did not fully trace these). | CVE Database V5 | ||
| Medium | – | MediumGCVE Database This update for jline3 fixes the following issue: Update to upstream version 3.30.17: * Security Fixes + Native Stack Buffer Overflow in Public INPUT_RECORD.memmove JNI Method (Windows) (GHSA-6r3w-6jpj-x5w6) + Authenticated SSH Shell Channel Resource Leak via Null or Non-Numeric PTY Dimensions (GHSA-7h86-pjwh-gpqj) + Authenticated SSH DoS via Unbounded Window-Change Terminal Geometry (GHSA-m935-wqpj-pvp3) + TCP Socket File Descriptor Leak When Maximum Connections Reached (GHSA-c87g-867h-cqr6) * Bug Fixes + strip control characters from file names in posix builtins + bound !# history expansion to prevent exponential blowup + verify server host keys in the ssh client builtin + address remaining security vulnerabilities reported by AFINE/CERT.PL + backport security fixes from master + backport security fixes to 3.x (path traversal + DSR plain text) + strip control characters from ssh banner and prompts * Dependency updates + bump com.diffplug.spotless:spotless-maven-plugin from 3.8.0 to 3.10.2 + bump slf4j.version from 2.0.18 to 2.0.19 + bump org.apache.maven.plugins:maven-surefire-plugin from 3.5.6 to 3.6.0 + bump org.apache.maven.plugins:maven-compiler-plugin from 3.15.0 to 3.16.0 + bump org.apache.felix:maven-bundle-plugin from 6.0.2 to 6.1.2 + bump actions/setup-java from 5 to 6.0.0 + bump org.graalvm.sdk:graal-sdk from 25.1.3 to 25.3.4.1 + bump com.mycila:license-maven-plugin from 5.0.0 to 5.1.2 + bump org.easymock:easymock from 5.6.0 to 5.7.0 + bump com.google.jimfs:jimfs from 1.3.1 to 1.3.2 + bump org.apache.maven.wrapper:maven-wrapper from 3.3.2 to 3.3.4 + bump org.apache.maven:apache-maven from 4.0.0-rc-3 to 4.0.0-rc-6 + bump eu.maveniverse.maven.njord:extension3 from 0.9.9 to 0.9.10 + bump com.palantir.javaformat:palantir-java-format from 2.96.0 to 2.97.0 + bump release-drafter/release-drafter from 7.6.0 to 7.7.0 + bump groovy.version from 4.0.32 to 4.0.33 + bump release-drafter/release-drafter from 7 to 7.6.0 + bump org.apache.maven.plugins:maven-jar-plugin from 3.5.0 to 3.5.1 - Update to upstream version 3.30.16 * bugfix release with security hardening, SSH agent forwarding fix, and terminal compatibility improvements. * Breaking Changes + SSH agent forwarding is no longer enabled by default; pass -A to explicitly request it + reject overlong hex components in OSC color responses + strip OSC and other escape sequences in ansiAppend + search multiple lib paths for versioned libutil.so + use Path.resolve instead of URI.resolve in cat and sort to prevent SSRF + check closed flag in PtyInputStream to prevent hang on empty input + confine ConfigurationPath lookups to the config directory + disable Read File command in nano restricted mode + drain buffered data before EOF in NonBlockingPumpInputStream + look up openpty in libc.so.6 for glibc 2.34+ + guard styleMatches and highlighter rules against ReDoS + backport telnet DoS mitigations (GHSA-47qp, GHSA-2r2c) + propagate EOF in PtyInputStream to avoid infinite loop + bump org.apache.ivy:ivy from 2.5.3 to 2.6.0 + bump actions/setup-node from 6 to 7 + bump com.palantir.javaformat:palantir-java-format from 2.94.0 to 2.96.0 + bump sshd.version from 2.18.0 to 2.19.0 + bump org.codehaus.gmavenplus:gmavenplus-plugin from 5.0.0 to 5.1.0 + bump org.graalvm.sdk:graal-sdk from 25.0.3 to 25.1.3 + bump com.diffplug.spotless:spotless-maven-plugin | GCVE Database | |||
| Medium | 6.5 | EPSS 0.1% | CVE-2026-91767php_openssl_matches_wildcard_name · Heap-buffer-overflow Medium6.5EPSS 0.1%GCVE DatabaseCVE-2026-91767 A heap-buffer-overflow vulnerability exists in the PHP function php_openssl_matches_wildcard_name() when processing TLS server certificates with wildcard names longer than the hostname being verified. This flaw allows a malicious server to cause the PHP client to read memory beyond the allocated heap buffer. The vulnerability is reachable by default because peer name verification is enabled by default in PHP client streams. It affects multiple PHP versions prior to fixed releases. | GCVE Database | ||
| Critical | 9.8 | EPSS 0.4% | Critical9.8EPSS 0.4%CERT/CCCVE-2026-96760 Authlib versions up to and including 1.7.2 contain a signature-verification bypass vulnerability in their JSON Web Signature (JWS) handling. The vulnerability allows attackers to supply JWS objects with an empty "signatures" array, which Authlib mistakenly treats as verified without performing signature checks. This enables attackers to forge arbitrary authenticated payloads without possessing any signing keys, potentially leading to authentication bypass, privilege escalation, and message integrity compromise. No official patch is currently available, and users should monitor the project's GitHub repository for updates. | CERT/CC |
Page 2 of 7 · 11 duplicate CVE records merged