{"items":[{"id":"NVI-00005118","kind":"vulnerability","title":"WebauthnAuthenticator leaks sensitive HTTP headers through INFO-level logs","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-q683-8468-r6h6"],"plain_summary":"GitHub lists this reviewed advisory for web-auth/webauthn-symfony-bundle. 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-4316a2ee4da84068ffcbc3e758ff8e8f"],"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},{"summary":"The original advisory lists fixed boundaries 5.3.4 for web-auth/webauthn-symfony-bundle. Confirm the publisher’s latest guidance.","source_ids":["sr-82aaf5fab64eb39e8c4ffab6b5989e2e"],"action_type":"vendor_patch","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":[],"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-4316a2ee4da84068ffcbc3e758ff8e8f","url":"https://github.com/advisories/GHSA-q683-8468-r6h6","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-q683-8468-r6h6","publisher":"GitHub Advisory Database","observed_at":"2026-11-05T19:05:53.922Z"},{"id":"sr-82aaf5fab64eb39e8c4ffab6b5989e2e","url":"https://github.com/advisories/GHSA-q683-8468-r6h6","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-q683-8468-r6h6","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:30.999Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-4316a2ee4da84068ffcbc3e758ff8e8f"],"technology":"web-auth/webauthn-symfony-bundle","known_exclusions":[],"conditions_summary":"## Impact\n\n`Webauthn\\Bundle\\Security\\Http\\Authenticator\\WebauthnAuthenticator` logs the full `Symfony\\Component\\HttpFoundation\\Request` object inside the log context of both `onAuthenticationSuccess()` and `onAuthenticationFailure()` at INFO level:\n\n```php\n$this->logger->info('User has been authenticated successfully with Webauthn.', [\n    'request' => $request,\n    'firewallName' => $firewallName,\n    'identifier' => $token->getUserIdentifier(),\n]);\n\n$this->logger->info('Webauthn authentication request failed.', [\n    'request' => $request,\n    'exception' => $exception,\n]);\n```\n\n`Request::__toString()` returns the raw HTTP message, including every request header. As soon as the configured logger normalises or stringifies the context (default behaviour for `LineFormatter`, `JsonFormatter` via `NormalizerFormatter`, etc.), sensitive headers such as `Cookie` (session identifier), `Authorization` and any custom auth header are written to the log stream in clear text.\n\nApplications that forward logs to centralised platforms (ELK, Splunk, Datadog and similar) are particularly exposed: log access is typically broader than application access, which can allow log readers to hijack authent","public_affected_ranges":["< 5.3.4"]},{"certainty":"source_listed","source_ids":["sr-82aaf5fab64eb39e8c4ffab6b5989e2e"],"technology":"web-auth/webauthn-symfony-bundle","known_exclusions":[],"conditions_summary":"## Impact\n\n`Webauthn\\Bundle\\Security\\Http\\Authenticator\\WebauthnAuthenticator` logs the full `Symfony\\Component\\HttpFoundation\\Request` object inside the log context of both `onAuthenticationSuccess()` and `onAuthenticationFailure()` at INFO level:\n\n```php\n$this->logger->info('User has been authenticated successfully with Webauthn.', [\n    'request' => $request,\n    'firewallName' => $firewallName,\n    'identifier' => $token->getUserIdentifier(),\n]);\n\n$this->logger->info('Webauthn authentication request failed.', [\n    'request' => $request,\n    'exception' => $exception,\n]);\n```\n\n`Request::__toString()` returns the raw HTTP message, including every request header. As soon as the configured logger normalises or stringifies the context (default behaviour for `LineFormatter`, `JsonFormatter` via `NormalizerFormatter`, etc.), sensitive headers such as `Cookie` (session identifier), `Authorization` and any custom auth header are written to the log stream in clear text.\n\nApplications that forward logs to centralised platforms (ELK, Splunk, Datadog and similar) are particularly exposed: log access is typically broader than application access, which can allow log readers to hijack authent","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 5.3.4"]}],"null_published_at":"2026-11-05T19:10:21.450Z","source_updated_at":"2026-06-26T21:00:50.000Z","source_disclosed_at":"2026-06-26T21:00:49.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Source facts changed; compare the preserved prior revision.","null_first_observed_at":"2026-10-31T21:42:30.999Z"},{"id":"NVI-00005118","kind":"vulnerability","title":"WebauthnAuthenticator leaks sensitive HTTP headers through INFO-level logs","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-q683-8468-r6h6"],"plain_summary":"OSV carries this publisher advisory for web-auth/webauthn-symfony-bundle. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 5.3.4 for web-auth/webauthn-symfony-bundle. Confirm the publisher’s latest guidance.","source_ids":["sr-82aaf5fab64eb39e8c4ffab6b5989e2e"],"action_type":"vendor_patch","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":[],"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-82aaf5fab64eb39e8c4ffab6b5989e2e","url":"https://github.com/advisories/GHSA-q683-8468-r6h6","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-q683-8468-r6h6","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:30.999Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-82aaf5fab64eb39e8c4ffab6b5989e2e"],"technology":"web-auth/webauthn-symfony-bundle","known_exclusions":[],"conditions_summary":"## Impact\n\n`Webauthn\\Bundle\\Security\\Http\\Authenticator\\WebauthnAuthenticator` logs the full `Symfony\\Component\\HttpFoundation\\Request` object inside the log context of both `onAuthenticationSuccess()` and `onAuthenticationFailure()` at INFO level:\n\n```php\n$this->logger->info('User has been authenticated successfully with Webauthn.', [\n    'request' => $request,\n    'firewallName' => $firewallName,\n    'identifier' => $token->getUserIdentifier(),\n]);\n\n$this->logger->info('Webauthn authentication request failed.', [\n    'request' => $request,\n    'exception' => $exception,\n]);\n```\n\n`Request::__toString()` returns the raw HTTP message, including every request header. As soon as the configured logger normalises or stringifies the context (default behaviour for `LineFormatter`, `JsonFormatter` via `NormalizerFormatter`, etc.), sensitive headers such as `Cookie` (session identifier), `Authorization` and any custom auth header are written to the log stream in clear text.\n\nApplications that forward logs to centralised platforms (ELK, Splunk, Datadog and similar) are particularly exposed: log access is typically broader than application access, which can allow log readers to hijack authent","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 5.3.4"]}],"null_published_at":"2026-10-31T22:13:01.442Z","source_updated_at":"2026-09-10T03:50:50.195Z","source_disclosed_at":"2026-06-26T21:00:49.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-10-31T21:42:30.999Z"}],"next_cursor":null,"snapshot_revision":"42594"}