Daily summary
Vulnerabilities of 19 November 2026: 581 new, 15 critical, 1 newly exploited
581 vulnerabilities added on 19 November 2026, 15 critical and 116 high: Remote code execution in WordPress plugins, TeamCity (182), AVideo (4) and more. 1 vulnerability newly listed as exploited by CISA.
- 15 critical
- 116 high
- 171 medium
- 34 low
- 245 unrated
- 1 newly exploited
Newly listed as exploited
Added to CISA's Known Exploited Vulnerabilities catalog: attackers use it.
Remote code execution in WordPress plugins
4 vulnerabilities
- 9.9WP Photo Album Plus
- 9.8WP DuplicateUnauthenticated Arbitrary File Upload to Remote Code Execution via 'files_data' Parameter in handle_batch_upload_files
- 8.0WP STAGINGAuthenticated (Subscriber+) PHP Object Injection to Remote Code Execution via Database Restore and Staging Reset
- 7.5WP DuplicateMissing Authorization to Authenticated (Subscriber+) Remote Code Execution via 'start_zip_creation' AJAX Action
TeamCity
182 vulnerabilities · Servers and applications
- 9.8In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 remote code execution was possible via external pull requests
- 8.8In JetBrains TeamCity before 2026.2.2, 2026.1.6 remote code execution was possible via Git submodule URLs
- 8.8In JetBrains TeamCity before 2026.2.2, 2026.1.6 remote code execution was possible via a time zone callback in the Kotlin DSL sandbox
- 8.8In JetBrains TeamCity before 2026.2.2, 2026.1.6 remote code execution was possible via a URL stream handler in the Kotlin DSL sandbox
- 8.8In JetBrains TeamCity before 2026.2.2, 2026.1.6 remote code execution was possible via Maven repository settings
Show 177 more
- 8.8In JetBrains TeamCity before 2026.2.1, 2026.1.5 privilege escalation was possible via username handling in token authentication
- 8.8In JetBrains TeamCity before 2026.2.1, 2026.1.5 remote code execution was possible via a UI patches callback in the Kotlin DSL sandbox
- 8.8In JetBrains TeamCity before 2026.2.1, 2026.1.5 remote code execution was possible via a context parameters callback in the Kotlin DSL sandbox
- 8.8In JetBrains TeamCity before 2026.2.1, 2026.1.5 remote code execution was possible via script definitions in the Kotlin DSL settings repository
- 8.8In JetBrains TeamCity before 2026.2.1, 2026.1.5 remote code execution was possible via boot classpath libraries in the Kotlin DSL sandbox
- 8.8In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 remote code execution was possible via a file write bypass in the Kotlin DSL sandbox
- 8.8In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 remote code execution was possible via Mercurial repository contents
- 8.8In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 remote code execution was possible via native code loading in the Kotlin DSL sandbox
- 8.4In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS on the P4 Code Review build tab was possible
- 8.1In JetBrains TeamCity before 2026.2.2, 2026.1.6 a CSRF attack was possible on the Hub integration settings
- 8.1In JetBrains TeamCity before 2026.2.2, 2026.1.6 the TFS helper process exposed an unauthenticated command server
- 8.1In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 project viewers could redirect GitHub App connection credentials of parent projects
- 8.1In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 missing authorization allowed any authenticated user to start and stop cloud agent instances
- 8.1In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 missing authorization allowed project viewers to remove VCS roots
- 8.1In JetBrains TeamCity before 2026.2 privilege escalation was possible via the authorization flow
- 8.0In JetBrains TeamCity before 2026.2.2, 2026.1.6 stored XSS on the Users page was possible
- 8.0In JetBrains TeamCity before 2026.2.2, 2026.1.6 stored XSS in Server Health reports was possible
- 8.0In JetBrains TeamCity before 2026.2.1, 2026.1.5 remote code execution was possible via Git VCS root settings
- 8.0In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS on the Issue Log tab was possible
- 7.7In JetBrains TeamCity before 2026.2.2 missing authorization allowed project developers to read arbitrary HashiCorp Vault secrets
- 7.7In JetBrains TeamCity before 2026.2.2, 2026.1.6 vCS root credentials could be exposed via change viewer links
- 7.7In JetBrains TeamCity before 2026.2.1 missing authorization allowed project viewers to download project settings
- 7.7In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 improper authorization allowed publishing packages to NuGet feeds of other projects
- 7.7In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 access keys of parent project AWS connections could be disclosed
- 7.7In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 improper authorization allowed access to credentials of other projects via build configuration settings
- 7.7In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 an SSRF in AWS connection settings could expose server credentials
- 7.7In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 an SSRF via pipeline repository branch listing was possible
- 7.6In JetBrains TeamCity before 2026.2.2, 2026.1.6 an XXE was possible in the TFS helper process
- 7.6In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS on build and queue pages was possible
- 7.6In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the AWS Credentials build feature was possible
- 7.6In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the NPM Registry build feature was possible
- 7.5In JetBrains TeamCity before 2026.2.2, 2026.1.6 a DoS attack was possible via unauthenticated multipart requests
- 7.5In JetBrains TeamCity before 2026.2.2, 2026.1.6 remote code execution was possible via Git VCS root URLs
- 7.5In JetBrains TeamCity before 2026.2.2, 2026.1.6 remote code execution was possible via local repository URLs in Subversion VCS roots
- 7.5In JetBrains TeamCity before 2026.2.1 remote code execution was possible via the Notification Rules form
- 7.5In JetBrains TeamCity before 2026.2.1, 2026.1.5 remote code execution was possible via personal builds with versioned settings
- 7.5In JetBrains TeamCity before 2026.2.1, 2026.1.5 remote code execution was possible via Mercurial subrepository paths
- 7.5In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 remote code execution was possible via build access codes disclosed to project users
- 7.5In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 remote code execution was possible via Mercurial VCS root settings
- 7.5In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 unauthenticated DoS via the agent protocol was possible
- 7.5In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 secure parameter values were disclosed to project viewers in pipelines
- 7.5In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 remote code execution was possible via Subversion VCS root settings
- 7.4In JetBrains TeamCity before 2026.2.2, 2026.1.6 agent Push authorization keys were predictable
- 7.4In JetBrains TeamCity before 2026.1.5 untrusted build approval for GitHub fork pull requests could be bypassed
- 7.2In JetBrains TeamCity before 2026.2.2, 2026.1.6 code injection in parent project Kotlin DSL was possible via subproject settings
- 7.2In JetBrains TeamCity before 2026.2.2, 2026.1.6 improper authorization allowed overwriting versioned settings of other projects
- 7.2In JetBrains TeamCity before 2026.2.2, 2026.1.6 remote code execution was possible via FreeMarker notification templates
- 7.2In JetBrains TeamCity before 2026.2.2, 2026.1.6 remote code execution was possible via Maven dependencies of Kotlin DSL settings
- 7.2In JetBrains TeamCity before 2026.2.2, 2026.1.6 remote code execution was possible via security context spoofing in the Kotlin DSL sandbox
- 7.2In JetBrains TeamCity before 2026.2.2, 2026.1.6 privilege escalation to system administrator was possible via Project Import
- 7.2In JetBrains TeamCity before 2026.2.1, 2026.1.5 code injection in generated Kotlin DSL was possible via matrix build parameters
- 7.2In JetBrains TeamCity before 2026.2.1, 2026.1.5 remote code execution was possible via Kotlin DSL compiler arguments
- 7.2In JetBrains TeamCity before 2026.2.1, 2026.1.5 remote code execution was possible via public reflection in the Kotlin DSL sandbox
- 7.2In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 remote code execution was possible via class injection in the Kotlin DSL sandbox
- 7.2In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 arbitrary file write on the server was possible via Kotlin DSL settings
- 7.2In JetBrains TeamCity before 2026.2, 2026.1.4 remote code execution was possible via Kubernetes Executor settings
- 7.1In JetBrains TeamCity before 2026.2.2, 2026.1.6 improper authorization allowed queuing builds with personal changes of other users
- 7.1In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 an LDAP injection allowed bypassing login restrictions
- 7.1In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 arbitrary file deletion on the server was possible via the Kotlin DSL sandbox
- 6.8In JetBrains TeamCity before 2026.2.2, 2026.1.6 stored XSS on the Projects Import page was possible
- 6.8In JetBrains TeamCity before 2026.2.2, 2026.1.6 stored XSS in the enforced settings restriction tooltip was possible
- 6.8In JetBrains TeamCity before 2026.2.2, 2026.1.6 command injection in Project Import artifact copy scripts was possible
- 6.8In JetBrains TeamCity before 2026.2.2 stored XSS in GitHub issue tracker suggestions was possible
- 6.8In JetBrains TeamCity before 2026.2.1, 2026.1.5 a DOM-based XSS in the plugin installation dialog was possible
- 6.8In JetBrains TeamCity before 2026.2.1, 2026.1.5 stored XSS in the Create Project dialog was possible
- 6.8In JetBrains TeamCity before 2026.2.1, 2026.1.5 stored and reflected XSS in Space project connection dialogs was possible
- 6.8In JetBrains TeamCity before 2026.2.1, 2026.1.5 stored XSS in the JaCoCo coverage settings was possible
- 6.8In JetBrains TeamCity before 2026.2.1 stored XSS in recipe export errors was possible
- 6.8In JetBrains TeamCity before 2026.2.1, 2026.1.5 stored XSS on the thread dump page was possible
- 6.8In JetBrains TeamCity before 2026.2.1 stored XSS in the Pull Requests health report for VCS roots was possible
- 6.8In JetBrains TeamCity before 2026.2.1 stored XSS in VMware vSphere cloud profile settings was possible
- 6.8In JetBrains TeamCity before 2026.2.1 stored XSS in the Pull Requests health report for Space connections was possible
- 6.8In JetBrains TeamCity before 2026.2.1, 2026.1.5 stored XSS in the Commit Status Publisher settings was possible
- 6.8In JetBrains TeamCity before 2026.2.1 stored XSS in the Amazon EC2 cloud profile editor was possible
- 6.8In JetBrains TeamCity before 2026.2.1 stored XSS in the Issue Trackers health report was possible
- 6.8In JetBrains TeamCity before 2026.2.1, 2026.1.5 stored XSS in the GitHub App repository selector was possible
- 6.8In JetBrains TeamCity before 2026.2.1 stored XSS in the Maven Build Info project header was possible
- 6.8In JetBrains TeamCity before 2026.2.1 stored XSS in Maven Build Info module links was possible
- 6.8In JetBrains TeamCity before 2026.2.1 stored XSS on the change Files tab was possible
- 6.8In JetBrains TeamCity before 2026.2.1 stored XSS in Git VCS root settings was possible
- 6.8In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS on the Report Tabs settings page was possible
- 6.8In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the build Report Tab dialog was possible
- 6.8In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in agent requirements was possible
- 6.8In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the checkout rules editor was possible
- 6.8In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the Schedule Trigger branch filter settings was possible
- 6.8In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in issue tracker links was possible
- 6.8In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the Inspections (IntelliJ IDEA) build step editor was possible
- 6.8In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the Agent Statistics tooltip was possible
- 6.8In JetBrains TeamCity before 2026.2, 2026.1.5 stored XSS on the external Kotlin DSL editor status page was possible
- 6.8In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the Promote build dialog for dependent builds was possible
- 6.8In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the Finish Build Trigger editor was possible
- 6.8In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the Schedule Trigger dependency settings was possible
- 6.8In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS on the build Issues tab was possible
- 6.8In JetBrains TeamCity before 2026.2, 2026.1.4 stored XSS in the Xcode runner configuration selection was possible
- 6.8In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the configuration health popup was possible
- 6.8In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the Maven settings health report was possible
- 6.8In JetBrains TeamCity before 2026.2 two-factor authentication bypass was possible via access token management
- 6.6In JetBrains TeamCity before 2026.2 privilege escalation of project-scoped access tokens via concurrent project deletion was possible
- 6.5In JetBrains TeamCity before 2026.2.2 a CSRF attack was possible on the diagnostic page
- 6.5In JetBrains TeamCity before 2026.2.2 vCS root passwords could be extracted via the REST API property locator
- 6.5In JetBrains TeamCity before 2026.2.1 missing authorization allowed reading VCS file contents and patches of other projects
- 6.5In JetBrains TeamCity before 2026.2.1 missing authorization allowed running modified build steps via pipeline debug runs
- 6.5In JetBrains TeamCity before 2026.2.1 missing authorization allowed guests to push VCS labels using stored VCS credentials
- 6.5In JetBrains TeamCity before 2026.2.1 the build parameter editor allowed project settings viewers to recover protected credentials
- 6.5In JetBrains TeamCity before 2026.2, 2026.1.4 arbitrary file write via read-write file channels in the Kotlin DSL sandbox was possible
- 6.4In JetBrains TeamCity before 2026.2.2 stored XSS in external change viewer links was possible
- 6.4In JetBrains TeamCity before 2026.2.1 stored XSS on the Changes page was possible
- 6.4In JetBrains TeamCity before 2026.2 credential leakage via Mercurial subrepository URLs was possible
- 6.1In JetBrains TeamCity before 2026.2.2, 2026.1.6 reflected XSS on the Edit VCS Root page was possible
- 6.1In JetBrains TeamCity before 2026.2.1 reflected XSS on the Cloud Profiles page was possible
- 6.1In JetBrains TeamCity before 2026.2, 2026.1.4 stored XSS in the JVM update warning on the Agent Summary page was possible
- 6.1In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 reflected XSS in the notification rule form was possible
- 6.1In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 reflected XSS on the Build Chains tab was possible
- 6.1In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 reflected XSS on the Clean-up Rules page was possible
- 6.1In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 reflected XSS in the inspection profile selector popup was possible
- 6.1In JetBrains TeamCity before 2026.2, 2026.1.5 reflected XSS on the Test History page was possible
- 6.1In JetBrains TeamCity before 2026.2 reflected XSS in Kubernetes cloud profile namespace and deployment choosers was possible
- 6.1In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 reflected XSS on the Build Log page was possible
- 6.1In JetBrains TeamCity before 2026.2, 2026.1.4 reflected XSS in the build log tree view was possible
- 6.1In JetBrains TeamCity before 2026.2, 2026.1.4 reflected XSS in build problem details was possible
- 6.1In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 reflected XSS on the build feature parameters page was possible
- 6.1In JetBrains TeamCity before 2026.2, 2026.1.4 reflected XSS on the notification rules page was possible
- 6.1In JetBrains TeamCity before 2026.2, 2026.1.4 stored XSS in the unified diff page syntax highlighting was possible
- 5.9In JetBrains TeamCity before 2026.2 remote code execution on build agents was possible via service message injection in build configuration names
- 5.9In JetBrains TeamCity before 2026.2 privilege escalation to system administrator was possible via project administrator roles in simple authorization mode
- 5.9In JetBrains TeamCity before 2026.2 improper authorization allowed project-limited access tokens to act with full permissions via XML-RPC
- 5.9In JetBrains TeamCity before 2026.2, 2026.1.4 authentication bypass via polling agent name rebinding was possible
- 5.4In JetBrains TeamCity before 2026.2.1 improper authorization allowed using AWS connections of other projects in cloud profiles
- 5.4In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the project Report Tab dialog was possible
- 5.4In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the Large Build Log health report was possible
- 5.4In JetBrains TeamCity before 2026.2 stored XSS on the Duplicates report tab was possible
- 5.4In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in build statistics charts was possible
- 5.4In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the checkout rules path preview was possible
- 5.4In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS on the diff view page was possible
- 5.4In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS on the Build Features page was possible
- 5.4In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the artifact dependency tree was possible
- 5.4In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS on the Triggers page was possible
- 5.4In JetBrains TeamCity before 2026.2, 2026.1.4 improper authorization allowed project agent administrators to manage agents of other projects
- 5.4In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the npm connection health report was possible
- 5.4In JetBrains TeamCity before 2026.2, 2026.1.4 stored XSS in Perforce job details was possible
- 5.4In JetBrains TeamCity before 2026.2 stored XSS in the duplicate remote parameter health report was possible
- 5.4In JetBrains TeamCity before 2026.2, 2026.1.4 improper authorization allowed users with the Run build permission to delete Perforce workspaces
- 5.3In JetBrains TeamCity before 2026.2.1 arbitrary file read was possible via symlinks in Mercurial subrepositories
- 5.3In JetBrains TeamCity before 2026.2 password parameters containing a caret were not masked in build logs on Windows
- 5.3In JetBrains TeamCity before 2026.2, 2026.1.4 unauthenticated extraction of build parameter values via a timing attack on build status icons was possible
- 4.9In JetBrains TeamCity before 2026.2.2, 2026.1.6 out-of-band data exfiltration via DNS resolution was possible in the Kotlin DSL sandbox
- 4.9In JetBrains TeamCity before 2026.2 project administrators could read OAuth connection secrets of ancestor projects
- 4.9In JetBrains TeamCity before 2026.2, 2026.1.4 the Perforce Administrator Access password could be written to the server log
- 4.8In JetBrains TeamCity before 2026.2 server certificates were not verified in the SVN integration
- 4.8In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS on the Versioned Settings page was possible
- 4.8In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS on the Slack Notifier settings page was possible
- 4.8In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS on the unknown VCS root page was possible
- 4.8In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the Pull Requests branch filter health report was possible
- 4.8In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS on the queued build Overview tab was possible
- 4.8In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in SSH key management was possible
- 4.7In JetBrains TeamCity before 2026.2, 2026.1.4 stored XSS in the Xcode runner SDK selection was possible
- 4.4In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS on the Test Details page was possible
- 4.3In JetBrains TeamCity before 2026.2, 2026.1.4 missing authorization allowed users to remove all build configuration assignments from an agent
- 4.3In JetBrains TeamCity before 2026.2 missing authorization in statistics chart export allowed viewing data of project
- 4.3In JetBrains TeamCity before 2026.2 missing authorization allowed reading Qodana reports of other projects
- 4.3In JetBrains TeamCity before 2026.2, 2026.1.4 an SSRF via connection tests was possible for users without project edit permissions
- 4.2In JetBrains TeamCity before 2026.2 poisoning of OAuth discovery metadata via the X-Forwarded-Host header was possible
- 3.7In JetBrains TeamCity before 2026.2.1, 2026.1.5 the TFS helper server was exposed on all network interfaces
- 3.7In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the notification rules editor was possible
- 3.5In JetBrains TeamCity before 2026.2.1, 2026.1.5 stored XSS on the Failure Conditions page was possible
- 3.5In JetBrains TeamCity before 2026.2.1, 2026.1.5 stored XSS in implicit agent requirements was possible
- 3.5In JetBrains TeamCity before 2026.2 stored XSS on the build step settings page was possible
- 3.5In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS on the SSH Keys page was possible
- 3.1In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the agent info popup was possible
- 3.1In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in Change Log revision tooltips was possible
- 3.1In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 reflected XSS on the Slack connection test page was possible
- 2.7In JetBrains TeamCity before 2026.2.2 the current request details debug endpoint exposed authentication headers and session cookies
- 2.7In JetBrains TeamCity before 2026.2 mute and unmute operations via XML-RPC could be attributed to other users
- 2.7In JetBrains TeamCity before 2026.2 the REST API exposed details of users not visible in the UI
- 2.7In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 the Cloud Profiles page disclosed cloud profiles of projects the user could not access
- 2.4In JetBrains TeamCity before 2026.2.2, 2026.1.6 hTML injection in pipeline notification emails was possible via user and job names
- 2.4In JetBrains TeamCity before 2026.2.2, 2026.1.6 hTML injection in pipeline notification emails was possible via commit messages
AVideo
4 vulnerabilities · Servers and applications
- 9.8Unauthenticated blind SQL injection in the video-list ORDER BY (incomplete fix of GHSA-pmmj-6425-gpgh) leaks `users.recoverPass`, leading to account takeover…
- 6.5Missing authentication in WWBNIndex `ajax.php` lets anonymous users de-index/re-index the platform, reset its WWBN key exchange state and purge the site cache
- 4.3IDOR in AI plugin `tabs/shorts.ajax.php` exposes other users' AI transcriptions and shorts suggestions for private videos
- 4.3YPTSocket broadcast lets unauthenticated callers inject HTML into admins' browsers
Splunk Enterprise
38 vulnerabilities · Servers and applications · most fixed in 10.0.12, 10.2.9, 10.4.5
- 9.4Authentication Bypass through the Cluster Configuration REST API in Splunk Enterprise
- 9.1Authentication Bypass through the RapidDiag REST API in Splunk Enterprise
- 8.8Improper Authorization through the REST API in Splunk Enterprise
- 8.8SPL Injection through the REST API in Splunk Enterprise
- 8.1SPL Injection through Metric Alert Filters in Splunk Enterprise
Show 33 more
- 7.6SPL Injection through Shared Dashboards in Splunk Enterprise
- 7.6SPL Injection through Classic Dashboard Searches in Splunk Enterprise
- 7.6Search Processing Language (SPL) Injection through Splunk Web in Splunk Enterprise
- 7.6SPL Injection through Analytics Workspace Metric Alerts in Splunk Enterprise
- 7.5Denial of Service (DoS) through Splunk-to-Splunk Data Forwarding in Splunk Enterprise
- 7.5Authentication Bypass through the REST API in Splunk Enterprise
- 7.5Authentication Bypass through the RapidDiag REST API in Splunk Enterprise
- 7.1SPL Command Safeguards Bypass through Cross-Site Request Forgery (CSRF) in Portable Document Format (PDF) Generation in Splunk Enterprise
- 7.1Search Processing Language (SPL) Injection in Data Model Acceleration in Splunk Enterprise
- 7.1SPL Injection through Saved Search Dispatch in Splunk Enterprise
- 6.5Denial of Service (DoS) through the Apps Backup and Restore REST API in Splunk Enterprise
- 6.5Path Traversal in Deployment Server Remote Input Listing in Splunk Enterprise
- 6.5Information Disclosure through the REST API and Splunk Web in Splunk Enterprise
- 6.5Improper Access Control through the REST API in Splunk Enterprise
- 6.4Privilege Escalation through Splunk Web Dashboards in Splunk App for Splunk Observability Cloud
- 6.4Stored Cross-Site Scripting (XSS) through Monitoring Console Platform Alerts in Splunk Enterprise
- 6.3SPL Injection through the rename Command in Splunk Enterprise
- 5.9Denial of Service (DoS) through HTTP PubSub Channel Subscriptions in Splunk Enterprise
- 5.9SPL Injection through Splunk Web Field Reports in Splunk Enterprise
- 5.4SPL Injection through Classic Dashboard in Splunk Enterprise
- 5.4Missing Authorization when Restoring Archived Indexed Data through the REST API in Splunk Enterprise
- 5.4SPL Injection through Data Model Regular Expression Field Preview in Splunk Enterprise
- 5.3Audit Log Injection through the REST API in Splunk Enterprise
- 4.8SPL Injection through Data Model Calculations in Splunk Enterprise
- 4.7Improper Input Validation during User Account Creation through the REST API in Splunk Enterprise for Windows
- 4.6Stored Cross-Site Scripting (XSS) through Splunk Web Views in Splunk Enterprise
- 4.3Improper Input Validation through HTTP Event Collector Token Names in Splunk Enterprise
- 4.3Sensitive Information Disclosure through the Deployment Server REST API in Splunk Enterprise
- 4.3Sensitive Information Disclosure through Knowledge Bundle Replication in Splunk Enterprise
- 4.3Missing Authorization for HTML-Based Views through the REST API in Splunk Enterprise
- 4.3Sensitive Information Disclosure through the Cluster Manager Bundle REST API in Splunk Enterprise
- 4.3Sensitive Information Disclosure through the Saved Searches REST API in Splunk Enterprise
- 4.2Improper Authentication Handling after Splunk Web Logout in Splunk Enterprise
PHP
17 vulnerabilities · Servers and applications · most fixed in 8.3.37, 8.4.28, 8.5.13
- 9.2PHP-FPM request smuggling through an unread HTTP request body
- 9.2Timezone cache use-after-free can lead to remote code execution
- 9.2Use-after-free after interrupted session shutdown
- 9.2Partially overwritten session files can lead to remote code execution
- 9.2Use-after-free in magic method backtraces can lead to remote code execution
Show 12 more
- 9.2Session serializer mismatch can lead to remote code execution
- 9.2Use-after-free via repopulation of last_fatal_error_backtrace global after shutdown
- 8.8PHP-FPM epoll use-after-free can lead to local privilege escalation
- 8.7Denial of service through folded HTTP response headers
- 8.2Mixed-case HTTPS and FTPS URLs can expose data in plaintext
- 7.7PHAR OpenSSL signature bypass via algorithm downgrade
- 6.9PHP-CGI out-of-bounds read and write during PATH_INFO correction
- 6.3Double free during DOM XML serialization
- 6.3SOAP information disclosure through malformed array dimensions
- 6.3Incorrect RFC 3986 URI serialization for oversized input
- 6.3SOAP use-after-free when processing DTD entity references
- 5.3PHP-FPM status endpoint XSS via unescaped user and script fields
Authentication bypass in servers and applications
1 vulnerability
Apache Tomcat
11 vulnerabilities · Servers and applications
- CriticalApache Tomcat: Cluster TLS-PSK configured to use TLS 1.3 does not validate peer
- HighApache Tomcat: ExpiresFilter removes existing Cache-Control: private header
- HighApache Tomcat: RewriteValve [F]/[G]/[R] rule matches do not stop processing
- HighApache Tomcat: HTTP/2 checks frame type before size leads to DoS
- HighApache Tomcat: Memory leak with OWB integration leads to DoS
Show 6 more
- MediumApache Tomcat: CGIServlet drops chunked POST body and can hang worker thread
- MediumApache Tomcat: Multiple vulnerabilities in EncryptInterceptor
- LowApache Tomcat: Memory leak on HTTP upgrade leads to DoS
- LowApache Tomcat: Fix for CVE-2026-25854 was incomplete
- LowApache Tomcat: Jakarta Authentication secureResponse AuthException sends unprotected HTTP 200 response
- LowApache Tomcat: Incorrect security-role-ref with RequestDispatcher.forward()
Broken access control in WordPress plugins
5 vulnerabilities
- 8.8WebToffee Product FeedAuthorization Bypass via Hard-coded Cron Salt
- 7.5Video Conferencing with Zoom
- 6.5Frontend Admin by DynamiApps
- 5.3Caddy WooCommerce Side CartMissing Authorization via saved-items REST endpoint
- 5.3AIKTPUnauthenticated Authorization Bypass via Predictable Token via Predictable 'aiktpz_token' + '/checkToken' Brute-Force Oracle
Portainer
11 vulnerabilities · Servers and applications · most fixed in 2.39.9, 2.45.4, 3.1.0
- 8.7Compose `use_api_socket` bypasses the Hide bind mounts for non-administrators setting
- 8.7Compose `profiles` and `include` bypass the environment security settings for non-administrators
- 7.1Cached ECR registry authorization token exposed to standard users in registry API responses
- 7.1Stored Git credentials can be sent to an attacker-chosen host by users with read-only access
- 7.1Stack update lets users take over and overwrite stacks on environments they cannot access
Show 6 more
- 6.5WebSocket attach and exec let users open a shell in containers they cannot access
- 6.1Git stack redeploy exposes stored environment variables of stacks on environments the user cannot access
- 6.0Stack list exposes Public stacks and their environment variables to users without access to the environment
- 5.3Docker network connect and disconnect let users attach or detach containers they cannot access
- 5.3Docker network resource control is not enforced when non-administrators attach containers, services, builds or stacks to a network
- 5.3Swarm service force-update lets users restart services they cannot access
Broken access control in servers and applications
4 vulnerabilities
- 8.5OpenVPNArgument injection in OpenVPN version 2.4.0 through 2.6.23 and 2.7_alpha1 through 2.7.8 on Windows allows local authenticated users to bypass interactive…
- 7.1GogsGogs through 0.14.4 Protected Branch Allowlist Bypass via Pull Request Merge
- 6.5Hestia Control PanelAuthenticated user can download another user's backup via username-prefix IDOR
- 5.3RedmineRedmine 6.1.0 before 6.1.6 and 7.0.0 before 7.0.3 OAuth Scope Bypass in Project Creation
Memory corruption in servers and applications
4 vulnerabilities
- 8.1BunBundled LSQUIC has a use-after-free in HTTP/3 header decoding
- 7.5ValkeyUse-after-free when client eviction frees the client whose command is still executing
- 7.4RubyRuby before 3.3.14, 3.4.13, and 4.0.10 has a heap-based buffer overflow during case conversion. One byte can be written outside a buffer for, for example,…
- 3.7GNU C LibraryDouble free after allocation failure in glob
Cross-site scripting in WordPress plugins
9 vulnerabilities
- 7.2SlimboxUnauthenticated Stored Cross-Site Scripting via Comment Anchor title Attribute
- 7.2WP-Slimbox2Unauthenticated Stored Cross-Site Scripting via Comment Link Title Attribute
- 7.2NextScripts: Social Networks Auto-PosterUnauthenticated Stored Cross-Site Scripting via 'comment_author' and 'comment_agent' Comment Fields
- 7.1Strong Testimonials
- 7.1Saphali Woocommerce Lite
Show 4 more
- 7.1Asset CleanUp: Page Speed Booster
- 6.4SlimboxAuthenticated (Subscriber+) Stored DOM-Based Cross-Site Scripting via Link 'title' Attribute via Slimbox Caption
- 6.4FoxtoolAuthenticated (Subscriber+) Stored Cross-Site Scripting via 'foxtool_image_id' Parameter
- 6.1Fancy LightboxUnauthenticated Stored Cross-Site Scripting via Comment Image Link 'title' Attribute
Linux kernel
246 vulnerabilities · Servers and applications · most fixed in 6.12.117, 6.18.61, 7.3.2
- 7.0ipv6: raw: fix use-after-free in rawv6_send_hdrinc()
- –ksmbd: wait for negotiation before receiving another PDU
- –smb: smbdirect: don't wait for RDMA_CM_EVENT_DISCONNECTED in smbdirect_socket_destroy_sync()
- –smb: smbdirect: release failed pending sockets of a listener
- –ksmbd: reject FSCTL_SET_ZERO_DATA on a directory handle
Show 241 more
- –fork: don't create io threads once PF_POSTCOREDUMP is set
- –wifi: mt76: mt7925: fix reset panic caused by the WM2 rx irq mask
- –ARM: 9524/1: mm: align hugetlb mappings to the huge page size
- –blk-crypto: fix NULL deref and UAF in __blk_crypto_evict_key()
- –ceph: fail readdir when the MDS reply carries no dirfrag
- –ksmbd: serialize directory emptiness checks with readdir
- –media: usbtv: fix null-pointer dereference on disconnect
- –net: usb: pegasus: do not advance rx_skb->data on dropped frames
- –nfsd: fix race between client_info_show() and free_client()
- –ocfs2/dlm: drain join handlers before releasing module text
- –ocfs2: drain quorum work before removing the cluster
- –ocfs2: pin owning modules for open debugfs files
- –smb: client: do not pass a NULL buf to is_oplock_break()
- –smb: client: fix early procfs exposure race
- –thunderbolt: Do not RPM complete unrelated subtrees on unplug
- –net/sched: cls_flower: avoid stale mask references after delete
- –driver core: take parent lock on deferred probe
- –Drivers: hv: vmbus: Bounds check the shared ring buffer indices
- –backlight: qcom-wled: Fix NULL pointer dereference in wled_remove()
- –ksmbd: deny access for an empty DACL instead of granting the request
- –ksmbd: fix OOB read and cross-share confusion in ksmbd_validate_name_reconnect()
- –ksmbd: fix parent dentry lifetime in directory enumeration
- –ksmbd: fix session reference leak on compounded SESSION_SETUP
- –ksmbd: ignore network devices of other namespaces
- –ksmbd: preserve unreadable named streams on open
- –ksmbd: prevent session binding in compound requests
- –ksmbd: prevent share root removal through empty paths
- –ksmbd: prevent stale data from being written by SMB2 WRITE requests
- –ksmbd: validate AppInstanceId takeover target
- –ksmbd: validate security descriptor offsets before pointer arithmetic
- –ksmbd: verify transform SessionId matches the decrypted header
- –cgroup: serialize migrations of newly forked processes
- –wifi: b43: fix use-after-free in b43_bcma_remove()
- –spmi: Fix potential use-after-free by grabbing of_node reference
- –SUNRPC: fix netns use-after-free in write_gssp()
- –smb: client: fix use-after-free infoleak via the readdir resume name
- –smb: client: fix use-after-free in cifs_ses_add_channel()
- –sched_ext: Fix use-after-free of a local reenq node left on an inactive cpu
- –RDMA/uverbs: Fix DMABUF use-after-free during ufile cleanup
- –RDMA/irdma: avoid use-after-free in icrdma_remove
- –rapidio: mport_cdev: fix use-after-free in mport_mm_close()
- –pps: generators: fix use-after-free when closing a removed device
- –PM: EM: Fix use-after-free of perf domain in netlink doit handlers
- –platform/x86: asus-wmi: fix use-after-free unregistering kbd_led led
- –nvmet: fix use-after-free of the old registrant in nvmet_pr_preempt()
- –nvmet-fc: fix use-after-free in nvmet_fc_ls_create_connection()
- –iommufd: Fix event queue release use-after-free
- –landlock: Fix superblock use-after-free in release_inode()
- –lockd: Fix use-after-free in nlmsvc_retry_blocked
- –media: au0828: fix use-after-free in bulk_timeout timer on disconnect
- –media: cx23885: Fix use-after-free in cx23885_finidev due to race condition
- –media: hackrf: fix use-after-free in hackrf_alloc_urbs() error path
- –media: imon: fix use-after-free in display_close via dev_dbg
- –media: ipu-bridge: Fix use-after-free in IVSC error path
- –mm/hugetlb: fix use-after-free in hugetlb_mfill_atomic_pte()
- –mm/hugetlb: fix use-after-free of a new anon folio
- –apparmor: fix a use-after-free in aa_lookupn_ns()
- –ASoC: audio-graph-card2: Fix use-after-free in audio_graph2_link_c2c()
- –ata: sata_fsl: Fix use-after-free of host_priv on probe() failure
- –s390/pci: Fix double-free and NULL deref in zpci MSI domain cleanup
- –s390/pci: Fix MSI directed-mode teardown IRQ bit count
- –s390/pci: Fix resource leak in zpci MSI setup
- –s390/pci: Fix use-after-free race in zpci floating interrupt cleanup
- –s390/kprobes: Prevent kprobes on instructions with exception table entry
- –s390/probes: Fix wrong opcode for cgrb fixup
- –s390/vmcp: Initialize full session info to zero
- –s390/zcrypt: Fix and improve zcrypt reply message verification checks
- –s390/zcrypt: Fix out-of-bounds ptr advance in cca_query_crypto_facility()
- –s390/zcrypt: Guard domain index uses against speculative bypass
- –HID: wacom: Advertise SW_MUTE_DEVICE capability prior to registration
- –HID: wacom: Fix Use-After-Free in wacom_intuos_pad
- –HID: wacom: Fix Use-After-Free in wacom_bamboo_pad
- –HID: wacom: Redesign shared sibling data lifecycle
- –klist: avoid accesses after waking klist_remove()
- –rust: bug: pass TAINT_WARN to warn_slowpath_fmt() on UML
- –rust: configfs: fix data offset calculation for subsystem callbacks
- –accel/amdxdna: clear the mailbox channel pointer when starting it fails
- –ALSA: emux: Fix UAF of soundfont zones at note-on
- –ALSA: pcmtest: handle multiple wraps in random capture fill
- –ASoC: amd: ps: fix snd_acp63_remove() teardown ordering
- –Bluetooth: hci_vhci: Pin module for debugfs file operations
- –drm/panthor: Fix TOCTOU race between GROUP_REGISTERED check and erase
- –fbdev: atmel_lcdfb: Prevent FIFO work after removal
- –filelock: keep superblock active through delegation wait
- –fs/proc/task_mmu: pin mm_users in do_pagemap_scan()
- –fsverity: Set S_VERITY only after rollback is no longer possible
- –genirq: Defer kfree(irqaction) until irq_thread_dtor() finishes
- –HID: hiddev: keep state alive through disconnect unlock
- –KVM: guest_memfd: Gracefully handle xarray errors when binding a memslot
- –KVM: pfncache: use a dedicated invalidation sequence for cache refresh
- –KVM: PPC: Book3S HV: Add SRCU protection for virtual-mode HPT hcalls
- –media: cx23885: unregister DVB bus when SP2 CI setup fails
- –media: gspca: use vb2_video_unregister_device() on disconnect
- –media: imx-jpeg: cancel timeout worker when streaming stops
- –media: marvell: mcam: stop DMA and cancel s_bh_work before freeing DMA buffers
- –media: microchip-csi2dc: fix async notifier leak on probe error path
- –media: microchip-isc: take a reference on the parsed endpoints
- –media: redrat3: fix UAF in probe error path leaving rc device registered
- –mm/rmap: don't discard lazyfree THPs at PMD level
- –mm/truncate: look up the end-edge straddler by index
- –mm: khugepaged: fix swap entry value to folio_pfn()
- –mptcp: hold MP_JOIN msk ref when cloning reqsk
- –mshv_vtl: detach poll waiter on POLLFREE
- –mtd: virt-concat: unlink discarded items before freeing
- –net: sched: prevent scheduling deactivated qdiscs
- –scsi: dc395x: sync the waiting_timer before freeing the host
- –serial: core: shut down initialized port on removal
- –staging: rtl8723bs: fix protected RX frame validation in decrypt path
- –xen-blkfront: unbind irq before tearing down ring and shadow requests
- –wifi: ath9k: delete channel-context timers on deinit
- –wifi: mt76: mt7996: unlink TWT flow if the MCU rejects the agreement
- –vfio/nvgrace-gpu: Use a core-only open_device in fallback mode
- –usb: gadget: fix refcount underflow in gadgetfs_bind() error path
- –ufs: use u64 for directory size in ufs_last_byte
- –spi: spi-pci1xxxx: quiesce DMA engines on transfer timeout
- –phy: core: Fix race-condition between _of_phy_get() and try_module_get()
- –power: supply: pf1550: drain IRQ work before unregistering supplies
- –power: supply: sbs-battery: disable polling before supply teardown
- –pps: generators: don't use the driver's info after unregister
- –nvmem: core: Fix OOB read for bit offsets of more than one byte
- –nvmet-auth: serialize access to DH-HMAC-CHAP state to fix UAF
- –media: rc: Ensure that rc_unregister_device() does not free input device
- –media: rc: Ensure registered is cleared in error path
- –media: rc: mce_kbd: Fix inconsistent locking of keylock
- –media: rc: Use after free in ir_raw_event_handle()
- –media: rc: After rc_unregister_device() timers can be re-armed
- –media: rc: Fix use after free in bpf progs
- –ocfs2/heartbeat: unlink live slots when their node is missing
- –ocfs2/dlm: hold a lock reference across grant AST enqueue
- –ocfs2/dlm: hold the lookup reference across convert AST enqueue
- –ocfs2: cancel quota sync work before freeing quota info
- –ocfs2: fix chunk number of the first chunk in a local quota file
- –ocfs2: pin refcount trees before dropping the lookup lock
- –ocfs2: snapshot dentry names in file and setattr traces
- –smb: client: fix OOB last_entry pointer from unbounded LastNameOffset
- –smb: client: hold server info until cifsd exits
- –ovl: hold a reference on the parent in readdir
- –ovl: set OVL_WHITEOUTS before publishing the upper dir
- –ovl: take a snapshot of the name for copy up
- –ovl: use the pinned upper dir in ovl_fix_origin()
- –ovl: always encode the origin fh when index is enabled
- –ovl: check that the parents of volatile/dirty are dirs
- –ovl: do not copy up a dentry that was removed
- –ovl: do not copy up an xattr value that was never read
- –ovl: fix a torn path in ovl_get_redirect()
- –ovl: read the nlink xattr of every indexed non-dir
- –ovl: set the revalidate flags after d_instantiate()
- –ovl: skip copy up of empty security.capability
- –xfs: fix buffer overruns in xfs_ioc_attr_list
- –xfs: avoid cross-rtgroup reaping after a repair
- –xfs: actually lock the metafile reservation when adjusting after repair
- –xfs: always reset incore attr fork buffer when resetting fork
- –xfs: don't fix the directory tree if live update fails
- –xfs: don't proceed with xattr repair if the live update fails
- –xfs: don't repair fs summary counters with garbage
- –xfs: fix lost errno returned from xfarray_foliosort
- –xfs: abort dirtree repair if the live update hook dies
- –xfs: check fork type against dabtree block magic number
- –netfilter: nft_payload: restrict checksum offsets to known values
- –xfs: mark overfull dabtree node blocks as corrupt
- –rtnetlink: wait for RCU readers in rtnl_link_unregister()
- –xfs: reject out-of-range attribute value lengths in xfs_attr_copy_value
- –xfs: reject remote xattr entries with an out-of-range value length
- –xfs: always forget cached ACLs if the attr fork swap succeeds
- –xfs: bound da-node entry count against the correct geometry
- –xfs: always report inode repair setup failures
- –xfs: bound inode fork length against the fork size during log recovery
- –xfs: complain loudly when dirtree checker finds broken links
- –xfs: don't overrun incore inode when cleaning attr forks
- –xfs: don't try to scrub self-referential dirent in metapath checker
- –xfs: don't subtract excess usage twice when computing agf_btreeblks
- –xfs: fix correction of unwritten extents in quota file data fork
- –smb: server: size directory name conversion buffer correctly
- –smb: smbdirect: fix buffer length underflow in RDMA transfers
- –smb: client: don't resurrect an exiting tcon from cached dir workers
- –smb: client: bound POSIX lock data area by response length
- –smb: client: fix buffer overflow in SMB2_tcon()
- –smb: client: fix OOB read of the resume name sent in TRANS2_FIND_NEXT2
- –smb: client: reclaim credits for decrypted reads with no matching mid
- –smb: client: reject FIND data areas that run past the received response
- –smb: client: reject short or out-of-range FIND response parameters
- –smb: client: validate NT transaction response layout and offsets
- –smb: client: validate SMB1 EA list bounds before parsing
- –pnfs/blocklayout: Complete a device upcall when the pipe is closed
- –NFSv4/pnfs: bound the CB_NOTIFY_DEVICEID array count before allocating
- –NFSv4/pnfs: Free the netid when draining a data-server address list
- –NFSv4/flexfiles: fail I/O to the data server once a lock is lost
- –NFSv4/flexfiles: Use the full 64-bit stripe_unit
- –NFS/localio: detect a short read or write before the iterator has moved
- –NFSD: cap the number of listeners accepted in listener_set
- –nfsd: clear XDR padding in GETXATTR replies
- –NFSD: copy SETXATTR data from all XDR buffer segments
- –NFSD: Destroy a recalled delegation the client does not hold
- –NFSD: Do not send CB_RECALL_ANY to NFSv4.0 clients
- –NFSD: Don't complete a cld upcall the daemon has not read
- –nfsd: don't modify a session slot when replaying its cached reply
- –nfsd: Fix id-to-name cache entry leak in idtoname_parse()
- –NFSD: Fix out-of-bounds read in the rpc_status dump
- –NFSD: Map flex file layout IDs through the request's user namespace
- –nfsd: preflight SEQUENCE replies before accepting a slot
- –nfsd: propagate SETXATTR value decode errors
- –NFSD: Set nn->cld_net before registering the cld pipe
- –NFSD: validate transport name in listener_set before serv creation
- –nfsd: zero NFSv4 COMPOUND tag padding
- –SUNRPC: Copy the deferred RPC Call from the head buffer
- –SUNRPC: Do not credit control-record octets to the RPC stream
- –SUNRPC: fix oversized GSS proxy token copy
- –sunrpc: pin gss module across auth_domain RCU free
- –SUNRPC: Reject a socket that already has an svc_sock attached
- –SUNRPC: trace an accepted transport before publishing it
- –sunrpc: treat empty auth.unix.gid replies as negative entries
- –rxrpc: Fix update of call->tx_pending without holding lock
- –rxrpc: Fix lack of short-send handling in rxrpc_kernel_send_data()
- –afs: Fix afs to abort the rxrpc call on send error
- –ALSA: x86: hdmi: fix chmap array missing terminator entry
- –KVM: SVM: Trigger new ASID allocation in both VMCBs on pCPU switch
- –KVM: nSVM: Reject KVM_SET_NESTED_STATE if L1 has EFER.LMA=1 && EFER.LME=0
- –KVM: x86/mmu: Bug the VM if KVM attempts to walk more levels than the MMU has
- –KVM: nSVM: Ignore EFER.LMA if EFER.LME=0 when preparing L2 state
- –KVM: x86/xen: Enforce 4-byte alignment of vcpu_info registration
- –KVM: x86: Request event processing for exception VM-Exits
- –KVM: x86: Take SRCU in kvm_zap_gfn_range()
- –KVM: x86: Zero reserved synic flags when delivering message to avoid stack leak
- –KVM: TDX: Enable Notify VM exit
- –KVM: TDX: Enable Bus Lock VM exit
- –KVM: guest_memfd: take the invalidate lock when unbinding a dying file
- –KVM: guest_memfd: Establish memslot<=>guest_memfd bindings *after* memslot is ready
- –KVM: PPC: Book3S HV: Add preempt_disable() around virtual-mode HPTE bit-lock users
- –HID: amd_sfh: Use report type from request node
- –HID: cp2112: validate response report lengths
- –HID: core: Fix out-of-bounds left shift by 32 in s32ton()
- –HID: mcp2200: validate READ_ALL response length
- –HID: mcp2221: always initialize and cancel init_work
- –HID: picoLCD: check for fb_deferred_io_init() error
- –HID: roccat: kovaplus: reject short button reports
- –HID: hid-lenovo-go-s: Add suspend function and gate access under bool.
- –HID: hid-lenovo-go-s: Prevent deadlock if device removed during setup
- –ksmbd: fix out-of-bounds read when padding the final compound response
- –ksmbd: fix invalid pointer dereference when get_inode_acl() fails
- –ksmbd: rebind completed CREATE replays without draining the old channel
- –rust_binder: wake epoll on self-work queued to poll thread
WordPress
19 vulnerabilities · WordPress core · most fixed in 6.6.12, 6.7.12, 6.8.13
- HighA reflected cross-site scripting (XSS) issue in the legacy media library popup
- HighA multisite privilege escalation issue letting a site Administrator take over a Super Admin account via Customizer menu previews
- HighAn unauthenticated privilege escalation issue via Template Part block attributes that could lead to remote code execution
- HighA cross-site scripting (XSS) issue in the block editor via Openverse image metadata
- HighAn unauthenticated stored cross-site scripting (XSS) issue via shortcode attributes in comments
Show 14 more
- MediumAn SQL injection issue in WP_Meta_Query via nested relation values
- MediumAn unauthenticated information disclosure issue exposing private taxonomy terms via the REST API search endpoint
- MediumAn SQL injection issue via the front page setting in Customizer changeset previews
- MediumAn unauthenticated denial of service issue via batched XML-RPC pingbacks
- MediumA Subscriber+ information disclosure issue via XML-RPC `wp.getComments`
- LowA cross-site scripting (XSS) issue in wp_interactivity_data_wp_context() via the store namespace
- LowA malformed regular expression that broadened JSON media type matching, fixed as a hardening measure
- LowAn Author+ information disclosure issue exposing user email addresses via the REST API comments endpoint
- LowA Contributor+ stored cross-site scripting (XSS) issue in the Comment Date block via its date format
- LowA Contributor+ cross-site scripting (XSS) issue via scripts in oEmbed provider responses
- LowAn Editor+ information disclosure issue via post and template author assignment in the REST API
- LowAn Administrator stored cross-site scripting (XSS) issue via Customizer previews
- LowAn Author+ authorization bypass issue via comment editing in the admin
- LowA Contributor+ stored cross-site scripting (XSS) issue in the block editor via media filenames
Mattermost
6 vulnerabilities · Servers and applications
- 6.5Missing nil check on decoded HTTP request body in Zoom plugin handlers
- 6.5Unbounded record hydration in the Playbooks GraphQL runs query
- 6.5Mattermost denial of service via unbounded memory allocation in ZIP archive processing
- 5.3Improper access control in the Mattermost GitLab plugin discloses confidential GitLab issues to unauthorized channel subscribers
- 5.0Missing channel permission check on Playbooks checklist slash command execution
- 4.5Information disclosure in Mattermost Server exposes database credentials via Support Packet
OpenProject
8 vulnerabilities · Servers and applications · most fixed in 17.9.8
- 4.3OpenProject invitation mails render the message as the inviter, leaking a private work package's subject
- 4.3Download location of external storage attachments ignores the virus scan status
- MediumPATCH /api/v3/meeting_outcomes/:id can move another user's outcome out of a meeting the caller may only view: the contract checks manage_outcomes on the new…
- MediumMissing authorization (CWE-862/CWE-639) in meeting agenda items new renders foreign meeting section titles
- MediumMissing authorization (CWE-862/CWE-639) in meeting agenda items cancel_new renders foreign meeting section titles
Show 3 more
- 3.5Server-side request forgery via Subversion and Git repository URLs
- 3.1Activity-details cache replays phase-journal details to users lacking view_project_phases
- 3.1API v3 work-package representer cache is shared across users with different custom-field visibility, leaking admin-only custom-field values to non-admins
Other vulnerabilities in servers and applications
9 vulnerabilities
- 8.5Frappe FrameworkUnauthorised sending of email in email communication due to missing validation
- 8.2Parse ServerQuery and LiveQuery subscription constraints disclose the auth data and session token of a user
- 7.2GravGrav 1.7: a user manager without super-admin access can take over a super-admin account from the classic admin Accounts page
- 6.4DiscourseRead-only API keys could authenticate users to sites connected through DiscourseConnect
- 5.4DiscourseSystem messages give the sender's authority to quoted member text
Show 4 more
- 5.3Dolibarr ERP CRMDolibarr ERP CRM Document Upload files.lib.php dol_convert_file code injection
- 4.9DiscourseWhisper content disclosed outside configured whisper groups
- LowHestia Control PanelPassword reset failures & 2FA reset failures are not logged
- LowHestia Control PanelOpen redirect in /login/ via the edit_link parameter (protocol-relative URL)
Other vulnerabilities in WordPress plugins
3 vulnerabilities
From NVD, the CVE Program, OSV.dev with the GitHub Advisory Database, WPVulnerability, WordPress's security advisories and CISA's Known Exploited Vulnerabilities catalog, as they stood when this was written. Each vulnerability's own page has its latest rating and fix. This product uses the NVD API but is not endorsed or certified by the NVD.