The internet is broken right now.
53 critical CVEs without a fix in the last 48 hours. Developers are crying quietly into their IDEs. 90 more already have a fix that someone still has to apply.
-
CVE-2026-132949
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 reflected XSS on the Clean-up Rules page was possible
-
CVE-2026-132951
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 reflected XSS in the notification rule form was possible
-
CVE-2026-132953
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS on the queued build Overview tab was possible
-
CVE-2026-132954
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS on the Triggers page was possible
-
CVE-2026-132939
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the Maven settings health report was possible
-
CVE-2026-132942
In JetBrains TeamCity before 2026.2, 2026.1.4 unauthenticated extraction of build parameter values via a timing attack on build status icons was possible
-
CVE-2026-132943
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 reflected XSS on the Build Log page was possible
-
CVE-2026-132945
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 reflected XSS in the inspection profile selector popup was possible
-
CVE-2026-132931
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 reflected XSS on the build feature parameters page was possible
-
CVE-2026-132932
In JetBrains TeamCity before 2026.2, 2026.1.4 reflected XSS in the build log tree view was possible
-
CVE-2026-132934
In JetBrains TeamCity before 2026.2, 2026.1.4 authentication bypass via polling agent name rebinding was possible
-
CVE-2026-132935
In JetBrains TeamCity before 2026.2 missing authorization in statistics chart export allowed viewing data of project
-
CVE-2026-132936
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the npm connection health report was possible
-
CVE-2026-132922
In JetBrains TeamCity before 2026.2, 2026.1.4 stored XSS in the unified diff page syntax highlighting was possible
-
CVE-2026-132925
In JetBrains TeamCity before 2026.2 stored XSS in the duplicate remote parameter health report was possible
-
CVE-2026-132926
In JetBrains TeamCity before 2026.2 poisoning of OAuth discovery metadata via the X-Forwarded-Host header was possible
-
CVE-2026-132929
In JetBrains TeamCity before 2026.2, 2026.1.4 reflected XSS on the notification rules page was possible
-
CVE-2026-132930
In JetBrains TeamCity before 2026.2, 2026.1.4 reflected XSS in build problem details was possible
-
CVE-2026-132914
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS on the Issue Log tab was possible
-
CVE-2026-132915
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 an LDAP injection allowed bypassing login restrictions
-
CVE-2026-132918
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS on build and queue pages was possible
-
CVE-2026-132921
In JetBrains TeamCity before 2026.2 two-factor authentication bypass was possible via access token management
-
CVE-2026-132913
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS on the P4 Code Review build tab was possible
-
CVE-2026-132899
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the NPM Registry build feature was possible
-
CVE-2026-112216
Vulnerability involving the exposure of sensitive information in the URLs of the UOC Virtual Campus’s document upload feature. After completing a document upload, the application includes identifiers related to the active session—such as `apjsessionid`—and other internal parameters associated with requests and users in the HTTP GET request parameters. This data may be stored in the browser history and in server or proxy logs, or transmitted via the HTTP Referer header, depending on the configuration and browsing flow. Its inclusion in the URL could allow for the unauthorized disclosure of information to third parties with access to those logs or recipients.
-
CVE-2026-126082
Active Storage makes it simple to upload and reference files in cloud services and attach those files to Active Record objects. Prior to 8.1.4.1 and 8.0.5.2, a Rails application that processes attachments with ImageMagick may allow an unauthenticated attacker to write arbitrary files on the server and, when attachments are stored with the Disk service, to read arbitrary files readable by the application process. Those files typically include secret_key_base and credentials for external systems, which may in turn allow escalation to remote code execution or lateral movement to those systems. ImageMagick selects a coder from the content of the file it is given, and some coders act on files named inside the image rather than on the image itself. Active Storage constrained none of ImageMagick's coders, and the ImageMagick analyzer runs when a file is attached, so an attacker who can upload a crafted file may be able to invoke one. Attaching the upload is sufficient; no variant, preview, or analyze call is required. One specific attack chain has been reported, but other attack chains may exist. An application is affected when it uses ImageMagick for Active Storage image processing through config.active_storage.variant_processor = :mini_magick, runs ImageMagick under a security policy that does not already deny the involved coders, and allows uploads from untrusted users. This issue is fixed in versions 8.1.4.1 and 8.0.5.2.