Skip to content

Product

redhat rhosemc vulnerabilities

48 published CVES affecting redhat rhosemc, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).

Total
48
Critical
4
High
27
Medium
15
Low
2
Unscored
0
CISA KEV
0

Latest redhat rhosemc CVEs

Newest publication first · page 1 of 2

  1. HighCVSS 7.0 EPSS 0.35%

    The webbrowser.open() API would accept leading dashes in the URL which could be handled as command line options for certain web browsers. New behavior rejects leading dashes. Users are recommended to sanitize URLs prior to passing to webbrowser.open().

  2. MediumCVSS 6.4 EPSS 0.21%

    A container privilege escalation flaw was found in certain AMQ Broker images. This issue stems from the /etc/passwd file being created with group-writable permissions during build time. In certain conditions, an attacker who can execute commands within an affected container, even...

  3. HighCVSS 7.5 EPSS 2.3%

    A flaw was found in Undertow where malformed client requests can trigger server-side stream resets without triggering abuse counters. This issue, referred to as the "MadeYouReset" attack, allows malicious clients to induce excessive server workload by repeatedly causing server-si...

  4. HighCVSS 7.8 EPSS 0.49%

    A flaw was found in linux-pam. The module pam_namespace may use access user-controlled paths without proper protection, allowing local users to elevate their privileges to root via multiple symlink attacks and race conditions.

  5. HighCVSS 7.3 EPSS 0.68%

    A vulnerability was found in Wildfly, where a user may perform Cross-site scripting in the Wildfly deployment system. This flaw allows an attacker or insider to execute a deployment with a malicious payload, which could trigger undesired behavior against the server.

  6. MediumCVSS 6.1 EPSS 2.1% Scanner template

    A misconfiguration flaw was found in Keycloak. This issue can allow an attacker to redirect users to an arbitrary URL if a 'Valid Redirect URI' is set to http://localhost or http://127.0.0.1, enabling sensitive information such as authorization codes to be exposed to the attacker...

Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.