{"items":[{"id":"NVI-00015269","kind":"vulnerability","title":"Apache Camel: KeycloakSecurityPolicy has Improper Authentication, Missing Authentication for Critical Function and Failing Open Vulnerabilities","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-qvc3-6q9x-95pj","CVE-2026-53913"],"plain_summary":"GitHub lists this reviewed advisory for org.apache.camel:camel-keycloak, org.apache.camel:camel-keycloak. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-146d294f96a508bd8e5aef3ed8ecf46f"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-07-24T16:47:32.000Z","value":"9.8 critical","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-4dbbb0cc06adc88453d5e342bbd9bb52"},{"kind":"EPSS","as_of":"2026-11-03T12:00:27.000Z","value":"1.085%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.65292. Missing scores are unknown.","source_id":"sr-146d294f96a508bd8e5aef3ed8ecf46f"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-4dbbb0cc06adc88453d5e342bbd9bb52","url":"https://github.com/advisories/GHSA-qvc3-6q9x-95pj","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-qvc3-6q9x-95pj","publisher":"GitHub Advisory Database","observed_at":"2026-11-03T09:59:13.529Z"},{"id":"sr-146d294f96a508bd8e5aef3ed8ecf46f","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-53913","publisher":"FIRST EPSS","observed_at":"2026-11-03T17:44:07.787Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-4dbbb0cc06adc88453d5e342bbd9bb52"],"technology":"org.apache.camel:camel-keycloak","known_exclusions":[],"conditions_summary":"Improper Authentication, Missing Authentication for Critical Function, Not Failing Securely ('Failing Open') vulnerability in Apache Camel Keycloak Component.\n\nThe KeycloakSecurityPolicy of camel-keycloak guards a route by running KeycloakSecurityProcessor.beforeProcess(), which performs three checks in sequence: it rejects a request that carries no access token, then - only if requiredRoles is non-empty - validates the roles, and - only if requiredPermissions is non-empty - validates the permissions. The actual cryptographic verification of the bearer access token (signature, issuer and expiry for a local JWT, or active-state and issuer for token introspection) is performed exclusively inside those role and permission checks. \n\nKeycloakSecurityPolicy defaults requiredRoles and requiredPermissions to empty - which is the documented 'Basic Setup' - so on a route configured that way the role and permission checks are skipped and the access token is therefore never verified. The token-presence check still rejects a missing token, but an invalid token is accepted: any non-null value in the Authorization: Bearer header - including an arbitrary string or a forged, unsigned JWT - passes t","public_affected_ranges":[">= 4.15.0, < 4.18.3"]},{"certainty":"source_listed","source_ids":["sr-4dbbb0cc06adc88453d5e342bbd9bb52"],"technology":"org.apache.camel:camel-keycloak","known_exclusions":[],"conditions_summary":"Improper Authentication, Missing Authentication for Critical Function, Not Failing Securely ('Failing Open') vulnerability in Apache Camel Keycloak Component.\n\nThe KeycloakSecurityPolicy of camel-keycloak guards a route by running KeycloakSecurityProcessor.beforeProcess(), which performs three checks in sequence: it rejects a request that carries no access token, then - only if requiredRoles is non-empty - validates the roles, and - only if requiredPermissions is non-empty - validates the permissions. The actual cryptographic verification of the bearer access token (signature, issuer and expiry for a local JWT, or active-state and issuer for token introspection) is performed exclusively inside those role and permission checks. \n\nKeycloakSecurityPolicy defaults requiredRoles and requiredPermissions to empty - which is the documented 'Basic Setup' - so on a route configured that way the role and permission checks are skipped and the access token is therefore never verified. The token-presence check still rejects a missing token, but an invalid token is accepted: any non-null value in the Authorization: Bearer header - including an arbitrary string or a forged, unsigned JWT - passes t","public_affected_ranges":[">= 4.19.0, < 4.21.0"]}],"null_published_at":"2026-11-06T00:29:57.321Z","source_updated_at":"2026-07-24T16:47:32.000Z","source_disclosed_at":"2026-07-06T09:30:30.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-11-03T09:59:13.529Z"},{"id":"NVI-00015269","kind":"vulnerability","title":"Apache Camel: KeycloakSecurityPolicy has Improper Authentication, Missing Authentication for Critical Function and Failing Open Vulnerabilities","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-qvc3-6q9x-95pj","CVE-2026-53913"],"plain_summary":"GitHub lists this reviewed advisory for org.apache.camel:camel-keycloak, org.apache.camel:camel-keycloak. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-4dbbb0cc06adc88453d5e342bbd9bb52"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-07-24T16:47:32.000Z","value":"9.8 critical","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-4dbbb0cc06adc88453d5e342bbd9bb52"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-4dbbb0cc06adc88453d5e342bbd9bb52","url":"https://github.com/advisories/GHSA-qvc3-6q9x-95pj","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-qvc3-6q9x-95pj","publisher":"GitHub Advisory Database","observed_at":"2026-11-03T09:59:13.529Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-4dbbb0cc06adc88453d5e342bbd9bb52"],"technology":"org.apache.camel:camel-keycloak","known_exclusions":[],"conditions_summary":"Improper Authentication, Missing Authentication for Critical Function, Not Failing Securely ('Failing Open') vulnerability in Apache Camel Keycloak Component.\n\nThe KeycloakSecurityPolicy of camel-keycloak guards a route by running KeycloakSecurityProcessor.beforeProcess(), which performs three checks in sequence: it rejects a request that carries no access token, then - only if requiredRoles is non-empty - validates the roles, and - only if requiredPermissions is non-empty - validates the permissions. The actual cryptographic verification of the bearer access token (signature, issuer and expiry for a local JWT, or active-state and issuer for token introspection) is performed exclusively inside those role and permission checks. \n\nKeycloakSecurityPolicy defaults requiredRoles and requiredPermissions to empty - which is the documented 'Basic Setup' - so on a route configured that way the role and permission checks are skipped and the access token is therefore never verified. The token-presence check still rejects a missing token, but an invalid token is accepted: any non-null value in the Authorization: Bearer header - including an arbitrary string or a forged, unsigned JWT - passes t","public_affected_ranges":[">= 4.15.0, < 4.18.3"]},{"certainty":"source_listed","source_ids":["sr-4dbbb0cc06adc88453d5e342bbd9bb52"],"technology":"org.apache.camel:camel-keycloak","known_exclusions":[],"conditions_summary":"Improper Authentication, Missing Authentication for Critical Function, Not Failing Securely ('Failing Open') vulnerability in Apache Camel Keycloak Component.\n\nThe KeycloakSecurityPolicy of camel-keycloak guards a route by running KeycloakSecurityProcessor.beforeProcess(), which performs three checks in sequence: it rejects a request that carries no access token, then - only if requiredRoles is non-empty - validates the roles, and - only if requiredPermissions is non-empty - validates the permissions. The actual cryptographic verification of the bearer access token (signature, issuer and expiry for a local JWT, or active-state and issuer for token introspection) is performed exclusively inside those role and permission checks. \n\nKeycloakSecurityPolicy defaults requiredRoles and requiredPermissions to empty - which is the documented 'Basic Setup' - so on a route configured that way the role and permission checks are skipped and the access token is therefore never verified. The token-presence check still rejects a missing token, but an invalid token is accepted: any non-null value in the Authorization: Bearer header - including an arbitrary string or a forged, unsigned JWT - passes t","public_affected_ranges":[">= 4.19.0, < 4.21.0"]}],"null_published_at":"2026-11-03T10:03:26.566Z","source_updated_at":"2026-07-24T16:47:32.000Z","source_disclosed_at":"2026-07-06T09:30:30.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-11-03T09:59:13.529Z"}],"next_cursor":null,"snapshot_revision":"42594"}