Critical security advisoryCriticalFlagged by our vulnerability database: PHP2Shell is on CISA’s exploited list. Most WordPress hosting runs PHP. See if your site is affectedFlagged by our vulnerability database: PHP2Shell is being exploited. DetailsExploited: PHP2Shell. Check your site
HuttenlocherTechnologies
Updated 7 h ago

Vulnerability database

Every flaw the U.S. government’s cybersecurity agency (CISA) has confirmed attackers are using, plus the new WordPress plugin and theme bugs published each day, sorted by what they mean for a small business. We refresh it twice a day. If you see something your website or office runs, tell us.

1,762exploited flaws on CISA’s list
34added in the last 30 days
344new WordPress flaws this week
390,080entries in the database

194 results · page 4 of 4

  • Jan 21, 2026A flaw was found in the Keycloak Admin REST API.CVE-2025-14083 · Other software · Red Hat · reported by Red HatLow 2.7

    A flaw was found in the Keycloak Admin REST API. This vulnerability allows the exposure of backend schema and rules, potentially leading to targeted attacks or privilege escalation via improper access control.

    Product
    Red Hat build of Keycloak 26.4
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Jan 21, 2026A flaw was found in the keycloak-services component of Keycloak.CVE-2025-14559 · Other software · Red Hat · reported by Red HatMedium 6.5

    A flaw was found in the keycloak-services component of Keycloak. This vulnerability allows the issuance of access and refresh tokens for disabled users, leading to unauthorized use of previously revoked privileges, via a business logic vulnerability in the Token Exchange implementation when a privileged client invokes the token exchange flow.

    Product
    Red Hat build of Keycloak 26.4
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Jan 21, 2026A flaw was found in the Keycloak server during refresh token processing, specifically in the TokenManager class responsible for enforcing refresh token reuse poCVE-2026-1035 · Other software · Red Hat · reported by Red HatLow 3.1

    A flaw was found in the Keycloak server during refresh token processing, specifically in the TokenManager class responsible for enforcing refresh token reuse policies. When strict refresh token rotation is enabled, the validation and update of refresh token usage are not performed atomically. This allows concurrent refresh requests to bypass single-use enforcement and issue multiple access tokens from the same refresh token. As a result, Keycloak’s refresh token rotation hardening can be undermined.

    Product
    Red Hat build of Keycloak 26.4
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Jan 20, 2026A flaw was identified in Keycloak’s OpenID Connect Dynamic Client Registration feature when clients authenticate using private_key_jwt.CVE-2026-1180 · Other software · Red Hat · reported by Red HatMedium 5.8

    A flaw was identified in Keycloak’s OpenID Connect Dynamic Client Registration feature when clients authenticate using private_key_jwt. The issue allows a client to specify an arbitrary jwks_uri, which Keycloak then retrieves without validating the destination. This enables attackers to coerce the Keycloak server into making HTTP requests to internal or restricted network resources. As a result, attackers can probe internal services and cloud metadata endpoints, creating an information disclosure and reconnaissance risk.

    Product
    Red Hat build of Keycloak 26.4
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Jan 15, 2026A flaw was found in Keycloak.CVE-2026-0976 · Other software · Red Hat · reported by Red HatLow 3.7

    A flaw was found in Keycloak. This improper input validation vulnerability occurs because Keycloak accepts RFC-compliant matrix parameters in URL path segments, while common reverse proxy configurations may ignore or mishandle them. A remote attacker can craft requests to mask path segments, potentially bypassing proxy-level path filtering. This could expose administrative or sensitive endpoints that operators believe are not externally reachable.

    Product
    Red Hat build of Keycloak 26.4.9
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Jan 7, 2026A flaw was found in Keycloak.CVE-2026-0707 · Other software · Red Hat · reported by Red HatMedium 5.3

    A flaw was found in Keycloak. The Keycloak Authorization header parser is overly permissive regarding the formatting of the "Bearer" authentication scheme. It accepts non-standard characters (such as tabs) as separators and tolerates case variations that deviate from RFC 6750 specifications.

    Product
    Red Hat build of Keycloak 26.4
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Dec 23, 2025A flaw was found in Keycloak.CVE-2025-11419 · Other software · Red Hat · reported by Red HatHigh 7.5

    A flaw was found in Keycloak. This vulnerability allows an unauthenticated remote attacker to cause a denial of service (DoS) by repeatedly initiating TLS 1.2 client-initiated renegotiation requests to exhaust server CPU resources, making the service unavailable.

    Product
    Red Hat build of Keycloak 26.0
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Dec 16, 2025A flaw was found in Keycloak.CVE-2025-14777 · Other software · Red Hat · reported by Red HatMedium 6

    A flaw was found in Keycloak. An IDOR (Broken Access Control) vulnerability exists in the admin API endpoints for authorization resource management, specifically in ResourceSetService and PermissionTicketService. The system checks authorization against the resourceServer (client) ID provided in the API request, but the backend database lookup and modification operations (findById, delete) only use the resourceId. This mismatch allows an authenticated attacker with fine-grained admin permissions for one client (e.g., Client A) to delete or update resources belonging to another client (Client B) within the same realm by supplying a valid resource ID.

    Product
    Red Hat build of Keycloak 26.4
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Dec 10, 2025A flaw was found in Keycloak Admin REST (Representational State Transfer) API.CVE-2025-14082 · Other software · Red Hat · reported by Red HatLow 2.7

    A flaw was found in Keycloak Admin REST (Representational State Transfer) API. This vulnerability allows information disclosure of sensitive role metadata via insufficient authorization checks on the /admin/realms/{realm}/roles endpoint.

    Product
    Red Hat build of Keycloak 26.4
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Jul 18, 2025A flaw was found in the Keycloak identity and access management system when Fine-Grained Admin Permissions(FGAPv2) are enabled.CVE-2025-7784 · Other software · Red Hat · reported by Red HatMedium 6.5

    A flaw was found in the Keycloak identity and access management system when Fine-Grained Admin Permissions(FGAPv2) are enabled. An administrative user with the manage-users role can escalate their privileges to realm-admin due to improper privilege enforcement. This vulnerability allows unauthorized elevation of access rights, compromising the intended separation of administrative duties and posing a security risk to the realm.

    Product
    Red Hat build of Keycloak 26
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Jul 10, 2025A flaw was found in Keycloak.CVE-2025-7365 · Other software · Red Hat · reported by Red HatHigh 7.1

    A flaw was found in Keycloak. When an authenticated attacker attempts to merge accounts with another existing account during an identity provider (IdP) login, the attacker will subsequently be prompted to "review profile" information. This vulnerability allows the attacker to modify their email address to match that of a victim's account, triggering a verification email sent to the victim's email address. The attacker's email address is not present in the verification email content, making it a potential phishing opportunity. If the victim clicks the verification link, the attacker can gain access to the victim's account.

    Product
    Red Hat build of Keycloak 26
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Jun 20, 2025A vulnerability has been identified in Keycloak that could lead to unauthorized information disclosure.CVE-2025-5416 · Other software · Red Hat · reported by Red HatLow 2.7

    A vulnerability has been identified in Keycloak that could lead to unauthorized information disclosure. While it requires an already authenticated user, the /admin/serverinfo endpoint can inadvertently provide sensitive environment information.

    Product
    Red Hat Build of Keycloak
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Apr 29, 2025A flaw was found in Keycloak.CVE-2025-3910 · Other software · Red Hat · reported by Red HatMedium 5.4

    A flaw was found in Keycloak. The org.keycloak.authorization package may be vulnerable to circumventing required actions, allowing users to circumvent requirements such as setting up two-factor authentication.

    Product
    Red Hat Build of Keycloak
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Apr 29, 2025A flaw was found in Keycloak.CVE-2025-3501 · Other software · Red Hat · reported by Red HatHigh 8.2

    A flaw was found in Keycloak. By setting a verification policy to 'ALL', the trust store certificate verification is skipped, which is unintended.

    Product
    Red Hat Build of Keycloak
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Mar 25, 2025A flaw was found in Keycloak.CVE-2025-2559 · Other software · Red Hat · reported by Red HatMedium 4.9

    A flaw was found in Keycloak. When the configuration uses JWT tokens for authentication, the tokens are cached until expiration. If a client uses JWT tokens with an excessively long expiration time, for example, 24 or 48 hours, the cache can grow indefinitely, leading to an OutOfMemoryError. This issue could result in a denial of service condition, preventing legitimate users from accessing the system.

    Product
    Red Hat Build of Keycloak
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Feb 18, 2025A vulnerability was found in Keycloak.CVE-2024-4028 · Other software · Red Hat · reported by Red HatLow 3.8

    A vulnerability was found in Keycloak. This issue may allow a privileged attacker to use a malicious payload as the permission while creating items (Resource and Permissions) from the admin console, leading to a stored cross-site scripting (XSS) attack.

    Product
    Red Hat Build of Keycloak
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Feb 17, 2025A flaw was found in the Keycloak organization feature, which allows the incorrect assignment of an organization to a user if their username or email matches theCVE-2025-1391 · Other software · Red Hat · reported by Red HatMedium 5.4

    A flaw was found in the Keycloak organization feature, which allows the incorrect assignment of an organization to a user if their username or email matches the organization’s domain pattern. This issue occurs at the mapper level, leading to misrepresentation in tokens. If an application relies on these claims for authorization, it may incorrectly assume a user belongs to an organization they are not a member of, potentially granting unauthorized access or privileges.

    Product
    Red Hat Build of Keycloak
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Jan 22, 2025A flaw was found in Keycloak.CVE-2025-0604 · Other software · Red Hat · reported by Red HatMedium 5.4

    A flaw was found in Keycloak. When an Active Directory user resets their password, the system updates it without performing an LDAP bind to validate the new credentials against AD. This vulnerability allows users whose AD accounts are expired or disabled to regain access in Keycloak, bypassing AD restrictions. The issue enables authentication bypass and could allow unauthorized access under certain conditions.

    Product
    Red Hat Build of Keycloak
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Jan 14, 2025A vulnerability was found in Keycloak.CVE-2024-11736 · Other software · Red Hat · reported by Red HatMedium 4.9

    A vulnerability was found in Keycloak. Admin users may have to access sensitive server environment variables and system properties through user-configurable URLs. When configuring backchannel logout URLs or admin URLs, admin users can include placeholders like ${env.VARNAME} or ${PROPNAME}. The server replaces these placeholders with the actual values of environment variables or system properties during URL processing.

    Product
    Red Hat build of Keycloak 26.0
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Jan 14, 2025A denial of service vulnerability was found in Keycloak that could allow an administrative user with the right to change realm settings to disrupt the service.CVE-2024-11734 · Other software · Red Hat · reported by Red HatMedium 6.5

    A denial of service vulnerability was found in Keycloak that could allow an administrative user with the right to change realm settings to disrupt the service. This action is done by modifying any of the security headers and inserting newlines, which causes the Keycloak server to write to a request that has already been terminated, leading to the failure of said request.

    Product
    Red Hat build of Keycloak 26.0
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Dec 17, 2024A vulnerability was found in Keycloak.CVE-2024-10973 · Other software · Red Hat · reported by Red HatMedium 5.7

    A vulnerability was found in Keycloak. The environment option `KC_CACHE_EMBEDDED_MTLS_ENABLED` does not work and the JGroups replication configuration is always used in plain text which can allow an attacker that has access to adjacent networks related to JGroups to read sensitive information.

    Product
    Red Hat Build of Keycloak
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Nov 25, 2024A vulnerability was found in the Keycloak Server.CVE-2024-9666 · Other software · Red Hat · reported by Red HatMedium 4.7

    A vulnerability was found in the Keycloak Server. The Keycloak Server is vulnerable to a denial of service (DoS) attack due to improper handling of proxy headers. When Keycloak is configured to accept incoming proxy headers, it may accept non-IP values, such as obfuscated identifiers, without proper validation. This issue can lead to costly DNS resolution operations, which an attacker could exploit to tie up IO threads and potentially cause a denial of service. The attacker must have access to send requests to a Keycloak instance that is configured to accept proxy headers, specifically when reverse proxies do not overwrite incoming headers, and Keycloak is configured to trust these headers.

    Product
    Red Hat build of Keycloak 24
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Nov 25, 2024A vulnerability was found in Keycloak.CVE-2024-10492 · Other software · Red Hat · reported by Red HatLow 2.7

    A vulnerability was found in Keycloak. A user with high privileges could read sensitive information from a Vault file that is not within the expected context. This attacker must have previous high access to the Keycloak server in order to perform resource creation, for example, an LDAP provider configuration and set up a Vault read file, which will only inform whether that file exists or not.

    Product
    Red Hat build of Keycloak 24
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Nov 25, 2024A flaw was found in Keycloak.CVE-2024-10451 · Other software · Red Hat · reported by Red HatMedium 5.9

    A flaw was found in Keycloak. This issue occurs because sensitive runtime values, such as passwords, may be captured during the Keycloak build process and embedded as default values in bytecode, leading to unintended information disclosure. In Keycloak 26, sensitive data specified directly in environment variables during the build process is also stored as a default values, making it accessible during runtime. Indirect usage of environment variables for SPI options and Quarkus properties is also vulnerable due to unconditional expansion by PropertyMapper logic, capturing sensitive data as default values in all Keycloak versions up to 26.0.2.

    Product
    Red Hat build of Keycloak 24
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Nov 25, 2024A vulnerability was found in the Keycloak-services package.CVE-2024-10270 · Other software · Red Hat · reported by Red HatMedium 6.5

    A vulnerability was found in the Keycloak-services package. If untrusted data is passed to the SearchQueryUtils method, it could lead to a denial of service (DoS) scenario by exhausting system resources due to a Regex complexity.

    Product
    Red Hat build of Keycloak 24
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Nov 17, 2024A flaw was found in Keycloak.CVE-2023-0657 · Other software · Red Hat · reported by Red HatLow 3.4

    A flaw was found in Keycloak. This issue occurs due to improperly enforcing token types when validating signatures locally. This could allow an authenticated attacker to exchange a logout token for an access token and possibly gain access to data outside of enforced permissions.

    Product
    Red Hat build of Keycloak 22
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Oct 9, 2024A flaw was found in Keycloak.CVE-2024-3656 · Other software · Red Hat · reported by Red HatHigh 8.1

    A flaw was found in Keycloak. Certain endpoints in Keycloak's admin REST API allow low-privilege users to access administrative functionalities. This flaw allows users to perform actions reserved for administrators, potentially leading to data breaches or system compromise.

    Product
    Red Hat Build of Keycloak
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Sep 19, 2024A misconfiguration flaw was found in Keycloak.CVE-2024-8883 · Other software · Red Hat · reported by Red HatMedium 6.1

    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, potentially leading to session hijacking.

    Product
    Red Hat Build of Keycloak
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Sep 19, 2024A flaw exists in the SAML signature validation method within the Keycloak XMLSignatureUtil class.CVE-2024-8698 · Other software · Red Hat · reported by Red HatHigh 7.7

    A flaw exists in the SAML signature validation method within the Keycloak XMLSignatureUtil class. The method incorrectly determines whether a SAML signature is for the full document or only for specific assertions based on the position of the signature in the XML document, rather than the Reference element used to specify the signed element. This flaw allows attackers to create crafted responses that can bypass the validation, potentially leading to privilege escalation or impersonation attacks.

    Product
    Red Hat Build of Keycloak
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Sep 9, 2024A session fixation issue was discovered in the SAML adapters provided by Keycloak.CVE-2024-7341 · Other software · Red Hat · reported by Red HatHigh 7.1

    A session fixation issue was discovered in the SAML adapters provided by Keycloak. The session ID and JSESSIONID cookie are not changed at login time, even when the turnOffChangeSessionIdOnLogin option is configured. This flaw allows an attacker who hijacks the current session before authentication to trigger session fixation.

    Product
    Red Hat Build of Keycloak
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Sep 9, 2024A vulnerability was found in Keycloak.CVE-2024-7318 · Other software · Red Hat · reported by Red HatMedium 4.8

    A vulnerability was found in Keycloak. Expired OTP codes are still usable when using FreeOTP when the OTP token period is set to 30 seconds (default). Instead of expiring and deemed unusable around 30 seconds in, the tokens are valid for an additional 30 seconds totaling 1 minute. A one time passcode that is valid longer than its expiration time increases the attack window for malicious actors to abuse the system and compromise accounts. Additionally, it increases the attack surface because at any given time, two OTPs are valid.

    Product
    Red Hat Build of Keycloak
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Sep 9, 2024An open redirect vulnerability was found in Keycloak.CVE-2024-7260 · Other software · Red Hat · reported by Red HatMedium 6.1

    An open redirect vulnerability was found in Keycloak. A specially crafted URL can be constructed where the referrer and referrer_uri parameters are made to trick a user to visit a malicious webpage. A trusted URL can trick users and automation into believing that the URL is safe, when, in fact, it redirects to a malicious server. This issue can result in a victim inadvertently trusting the destination of the redirect, potentially leading to a successful phishing attack or other types of attacks. Once a crafted URL is made, it can be sent to a Keycloak admin via email for example. This will trigger this vulnerability when the user visits the page and clicks the link. A malicious actor can use this to target users they know are Keycloak admins for further attacks. It may also be possible to bypass other domain-related security checks, such as supplying this as a OAuth redirect uri. The malicious actor can further obfuscate the redirect_uri using URL encoding, to hide the text of the actual malicious website domain.

    Product
    Red Hat Build of Keycloak
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Sep 3, 2024A vulnerability was found in Keycloak.CVE-2024-4629 · Other software · Red Hat · reported by Red HatMedium 6.5

    A vulnerability was found in Keycloak. This flaw allows attackers to bypass brute force protection by exploiting the timing of login attempts. By initiating multiple login requests simultaneously, attackers can exceed the configured limits for failed attempts before the system locks them out. This timing loophole enables attackers to make more guesses at passwords than intended, potentially compromising account security on affected systems.

    Product
    Red Hat Build of Keycloak
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Jun 18, 2024A vulnerability was found in Keycloak.CVE-2024-5967 · Other software · Red Hat · reported by Red HatLow 2.7

    A vulnerability was found in Keycloak. The LDAP testing endpoint allows changing the Connection URL  independently without re-entering the currently configured LDAP bind credentials. This flaw allows an attacker with admin access (permission manage-realm) to change the LDAP host URL ("Connection URL") to a machine they control. The Keycloak server will connect to the attacker's host and try to authenticate with the configured credentials, thus leaking them to the attacker. As a consequence, an attacker who has compromised the admin console or compromised a user with sufficient privileges can leak domain credentials and attack the domain.

    Product
    Red Hat Build of Keycloak
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Jun 3, 2024A flaw was found in Keycloak in OAuth 2.0 Pushed Authorization Requests (PAR).CVE-2024-4540 · Other software · Red Hat · reported by Red HatHigh 7.5

    A flaw was found in Keycloak in OAuth 2.0 Pushed Authorization Requests (PAR). Client-provided parameters were found to be included in plain text in the KC_RESTART cookie returned by the authorization server's HTTP response to a `request_uri` authorization request, possibly leading to an information disclosure vulnerability.

    Product
    Red Hat Build of Keycloak
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Apr 25, 2024A flaw was found in Keycloak that occurs from an error in the re-authentication mechanism within org.keycloak.authentication.CVE-2023-6787 · Other software · Red Hat · reported by Red HatMedium 6.5

    A flaw was found in Keycloak that occurs from an error in the re-authentication mechanism within org.keycloak.authentication. This flaw allows hijacking an active Keycloak session by triggering a new authentication process with the query parameter "prompt=login," prompting the user to re-enter their credentials. If the user cancels this re-authentication by selecting "Restart login," an account takeover may occur, as the new session, with a different SUB, will possess the same SID as the previous session.

    Product
    Red Hat build of Keycloak 22
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Apr 25, 2024A flaw was found in the Keycloak package.CVE-2023-6544 · Other software · Red Hat · reported by Red HatMedium 5.4

    A flaw was found in the Keycloak package. This issue occurs due to a permissive regular expression hardcoded for filtering which allows hosts to register a dynamic client. A malicious user with enough information about the environment could jeopardize an environment with this specific Dynamic Client Registration and TrustedDomain configuration previously unauthorized.

    Product
    Red Hat build of Keycloak 22
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Apr 25, 2024A log injection flaw was found in Keycloak.CVE-2023-6484 · Other software · Red Hat · reported by Red HatMedium 5.3

    A log injection flaw was found in Keycloak. A text string may be injected through the authentication form when using the WebAuthn authentication mode. This issue may have a minor impact to the logs integrity.

    Product
    Red Hat build of Keycloak 22
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Apr 25, 2024A flaw was found in Keycloak, where it does not correctly validate its client step-up authentication in org.keycloak.authentication.CVE-2023-3597 · Other software · Red Hat · reported by Red HatMedium 5

    A flaw was found in Keycloak, where it does not correctly validate its client step-up authentication in org.keycloak.authentication. This flaw allows a remote user authenticated with a password to register a false second authentication factor along with an existing one and bypass authentication.

    Product
    Red Hat build of Keycloak 22
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Apr 17, 2024A flaw was found in Keycloak's redirect_uri validation logic.CVE-2024-2419 · Other software · Red Hat · reported by Red HatHigh 7.1

    A flaw was found in Keycloak's redirect_uri validation logic. This issue may allow a bypass of otherwise explicitly allowed hosts. A successful attack may lead to the theft of an access token, making it possible for the attacker to impersonate other users. It is very similar to CVE-2023-6291.

    Product
    Red Hat build of Keycloak 22
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Feb 28, 2024A flaw was found in Keycloak.CVE-2024-1722 · Other software · Red Hat · reported by Red HatLow 3.7

    A flaw was found in Keycloak. In certain conditions, this issue may allow a remote unauthenticated attacker to block other accounts from logging in.

    Product
    Red Hat Build of Keycloak
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Jan 26, 2024A flaw was found in the redirect_uri validation logic in Keycloak.CVE-2023-6291 · Other software · Red Hat · reported by Red HatHigh 7.1

    A flaw was found in the redirect_uri validation logic in Keycloak. This issue may allow a bypass of otherwise explicitly allowed hosts. A successful attack may lead to an access token being stolen, making it possible for the attacker to impersonate other users.

    Product
    Red Hat build of Keycloak 22
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Dec 18, 2023A flaw was found in Keycloak.CVE-2023-6927 · Other software · Red Hat · reported by Red HatMedium 4.6

    A flaw was found in Keycloak. This issue may allow an attacker to steal authorization codes or tokens from clients using a wildcard in the JARM response mode "form_post.jwt" which could be used to bypass the security patch implemented to address CVE-2023-6134.

    Product
    Red Hat build of Keycloak 22
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Dec 14, 2023A flaw was found in Keycloak that prevents certain schemes in redirects, but permits them if a wildcard is appended to the token.CVE-2023-6134 · Other software · Red Hat · reported by Red HatMedium 4.6

    A flaw was found in Keycloak that prevents certain schemes in redirects, but permits them if a wildcard is appended to the token. This issue could allow an attacker to submit a specially crafted request leading to cross-site scripting (XSS) or further attacks. This flaw is the result of an incomplete fix for CVE-2020-10748.

    Product
    Red Hat build of Keycloak 22
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.

Where this comes from: the exploited list is CISA’s Known Exploited Vulnerabilities catalog. Everything else is the whole National Vulnerability Database, where each record is published by the team that found the bug (Wordfence, Patchstack, WPScan, the vendors themselves and others); we show who. Exploit odds are FIRST’s EPSS, updated daily. Titles and categories are ours, so check the linked record before acting on a detail. For a write-up of the big ones, see our advisories. Every vendor, and every WordPress plugin and theme with a recorded flaw, also has its own page. All of it is free to reuse as JSON, CSV or RSS.

Weekly security brief

The flaws that hit local websites, every Friday.

One short email: what got exploited this week, which WordPress plugins broke, and what to check. Unsubscribe in one click.

Get in touch

Tell us what you're building.

A website, your marketing, a security check, an app, or the thing you've been running out of a spreadsheet for three years. A few lines is plenty.

01The person who'll do the work writes back
02A short call, then a written plan with the price
03Nothing starts until you say yes
04Hacked or down right now? Call, and we pick up the same day
843-331-6339

Not ready to talk yet? Run the free website check and see what Google sees.

What do you need?
Build
Grow
Protect
Urgent

No newsletter, no sales sequence. Just a reply.