10516 matches found
PT-2025-18290 · Discourse · Discourse
Name of the Vulnerable Software and Affected Versions: Discourse versions prior to 3.4.3 Discourse versions prior to 3.5.0.beta3 Description: Discourse is an open-source discussion platform. In versions prior to 3.4.3 on the stable branch and 3.5.0.beta3 on the beta branch, the user limit for a...
CVE-2025-32376: Improper Access Control
Discourse is an open-source discussion platform. Prior to versions 3.4.3 on the stable branch and 3.5.0.beta3 on the beta branch, the users limit for a DM can be bypassed, thus giving the ability to potentially create a DM with every user from a site in it. This issue has been patched in stable...
Medium: runc
Issue Overview: Reader.Read does not set a limit on the maximum size of file headers. A maliciously crafted archive could cause Read to allocate unbounded amounts of memory, potentially causing resource exhaustion or panics. After fix, Reader.Read limits the maximum size of header blocks to 1 MiB...
Amazon Linux 2 : runc (ALASECS-2025-058)
The version of runc installed on the remote host is prior to 1.1.4-1. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2ECS-2025-058 advisory. Reader.Read does not set a limit on the maximum size of file headers. A maliciously crafted archive could cause Read to...
Important: redis6
Issue Overview: Redis is an open source, in-memory database that persists on disk. In versions starting at 2.6 and prior to 7.4.3, An unauthenticated client can cause unlimited growth of output buffers, until the server runs out of memory or is killed. By default, the Redis configuration does not...
Medium: runc
Issue Overview: Reader.Read does not set a limit on the maximum size of file headers. A maliciously crafted archive could cause Read to allocate unbounded amounts of memory, potentially causing resource exhaustion or panics. After fix, Reader.Read limits the maximum size of header blocks to 1 MiB...
Medium: containerd
Issue Overview: Reader.Read does not set a limit on the maximum size of file headers. A maliciously crafted archive could cause Read to allocate unbounded amounts of memory, potentially causing resource exhaustion or panics. After fix, Reader.Read limits the maximum size of header blocks to 1 MiB...
Medium: docker
Issue Overview: Reader.Read does not set a limit on the maximum size of file headers. A maliciously crafted archive could cause Read to allocate unbounded amounts of memory, potentially causing resource exhaustion or panics. After fix, Reader.Read limits the maximum size of header blocks to 1 MiB...
Medium: runc
Issue Overview: Reader.Read does not set a limit on the maximum size of file headers. A maliciously crafted archive could cause Read to allocate unbounded amounts of memory, potentially causing resource exhaustion or panics. After fix, Reader.Read limits the maximum size of header blocks to 1 MiB...
Medium: containerd
Issue Overview: Reader.Read does not set a limit on the maximum size of file headers. A maliciously crafted archive could cause Read to allocate unbounded amounts of memory, potentially causing resource exhaustion or panics. After fix, Reader.Read limits the maximum size of header blocks to 1 MiB...
Medium: containerd
Issue Overview: Reader.Read does not set a limit on the maximum size of file headers. A maliciously crafted archive could cause Read to allocate unbounded amounts of memory, potentially causing resource exhaustion or panics. After fix, Reader.Read limits the maximum size of header blocks to 1 MiB...
Medium: docker
Issue Overview: Reader.Read does not set a limit on the maximum size of file headers. A maliciously crafted archive could cause Read to allocate unbounded amounts of memory, potentially causing resource exhaustion or panics. After fix, Reader.Read limits the maximum size of header blocks to 1 MiB...
CVE-2025-43014
In JetBrains Toolbox App before 2.6 the SSH plugin established connections without sufficient user confirmation...
CVE-2025-39577
Improper Neutralization of Input During Web Page Generation 'Cross-site Scripting' vulnerability in Property Hive PropertyHive propertyhive allows Stored XSS.This issue affects PropertyHive: from n/a through = 2.1.2...
CVE-2025-0101
A low privileged user can set the date of the devices to the 19th of January 2038 an therefore exceed the 32-Bit time limit. This causes some functions to work unexpected or stop working at all. Both during runtime and after a restart...
GraphQL Armor Cost-Limit Plugin Bypass via Introspection Query Obfuscation
Summary A query cost restriction using the cost-limit can be bypassed if ignoreIntrospection is enabled which is the default configuration by naming your query/fragment schema. Details At the start of the computeComplexity function, we have the following check for ignoreIntrospection option: ts i...
GHSA-733V-P3H5-QPQ7 GraphQL Armor Cost-Limit Plugin Bypass via Introspection Query Obfuscation
Summary A query cost restriction using the cost-limit can be bypassed if ignoreIntrospection is enabled which is the default configuration by naming your query/fragment schema. Details At the start of the computeComplexity function, we have the following check for ignoreIntrospection option: ts i...
@cedarjs/api-server (>=0.0.4, <=9.0.0-canary.1784), @cedarjs/api-server-watch (>=5.0.7-next.219, <=9.0.0-canary.3124) +54 more potentially affected by unknown CVE via @escape.tech/graphql-armor-cost-limit (>=2.0.0, <=2.4.1)
@escape.tech/graphql-armor-cost-limit NPM version =2.0.0, =0.0.4, =5.0.7-next.219, =0.0.4, =5.0.4-next.167, =0.0.4, =0.0.4, =0.0.4, =0.0.4, =0.0.4, =0.0.4, =0.9.1-next.19, =6.0.3-next.227, =0.0.4, =6.0.3-next.227, =0.0.4, =9.0.0-canary.3124 and more Source cves: unknown CVE Source advisory:...
@cedarjs/api-server (>=0.0.4, <=9.0.0-canary.1784), @cedarjs/api-server-watch (>=5.0.7-next.219, <=9.0.0-canary.3124) +54 more potentially affected by unknown CVE via @escape.tech/graphql-armor-cost-limit (>=2.0.0, <=2.4.1)
@escape.tech/graphql-armor-cost-limit NPM version =2.0.0, =0.0.4, =5.0.7-next.219, =0.0.4, =5.0.4-next.167, =0.0.4, =0.0.4, =0.0.4, =0.0.4, =0.0.4, =0.0.4, =0.9.1-next.19, =6.0.3-next.227, =0.0.4, =6.0.3-next.227, =0.0.4, =9.0.0-canary.3124 and more Source cves: unknown CVE Source advisory:...
PT-2025-19360 · Npm · @Escape.Tech/Graphql-Armor-Cost-Limit
Summary A query cost restriction using the cost-limit can be bypassed if ignoreIntrospection is enabled which is the default configuration by naming your query/fragment schema. Details At the start of the computeComplexity function, we have the following check for ignoreIntrospection option: ts i...