{"items":[{"id":"NVI-00010722","kind":"vulnerability","title":"better-auth: Device login approval does not show the requesting client or permissions","revision":4,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-q84f-53jg-9ppm","CVE-2026-109346"],"plain_summary":"GitHub lists this reviewed advisory for better-auth. 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-02cd84d525b9e18c0afa69bc9274e228"],"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 1.7.0-rc.3 for better-auth. Confirm the publisher’s latest guidance.","source_ids":["sr-8aa0a2040a7a7baccd6228c0f61d2df6"],"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":[{"kind":"CVSS","as_of":"2026-10-27T14:49:54.000Z","value":"8.1 high","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-cdaefbeb4d60307bac0151ef3d5bcdaa"},{"kind":"CVSS","as_of":"2026-10-26T17:17:13.120Z","value":"8.1 HIGH (3.1)","meaning":"disclosure@vulncheck.com severity; no combined Null risk score.","source_id":"sr-2ca5f4309a847cef4965ddda99b7a771"},{"kind":"CVSS","as_of":"2026-10-26T17:17:13.120Z","value":"8.5 HIGH (4.0)","meaning":"disclosure@vulncheck.com severity; no combined Null risk score.","source_id":"sr-2ca5f4309a847cef4965ddda99b7a771"},{"kind":"EPSS","as_of":"2026-11-04T12:03:12.000Z","value":"0.278%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.20389. Missing scores are unknown.","source_id":"sr-02cd84d525b9e18c0afa69bc9274e228"}],"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-cdaefbeb4d60307bac0151ef3d5bcdaa","url":"https://github.com/advisories/GHSA-q84f-53jg-9ppm","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-q84f-53jg-9ppm","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T22:06:46.371Z"},{"id":"sr-8aa0a2040a7a7baccd6228c0f61d2df6","url":"https://github.com/advisories/GHSA-q84f-53jg-9ppm","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-q84f-53jg-9ppm","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-11-03T17:42:53.459Z"},{"id":"sr-2ca5f4309a847cef4965ddda99b7a771","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-109346","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-109346","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-07T00:52:23.335Z"},{"id":"sr-02cd84d525b9e18c0afa69bc9274e228","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-109346","publisher":"FIRST EPSS","observed_at":"2026-11-04T17:58:50.311Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-cdaefbeb4d60307bac0151ef3d5bcdaa"],"technology":"better-auth","known_exclusions":[],"conditions_summary":"## Am I affected?\n\nYou may be affected if you use `better-auth` from `1.3.8-beta.3` up to, but not including, `1.7.0-rc.3`, and you enable the `deviceAuthorization()` plugin. This range includes all 1.6 releases.\n\nYou are affected only if all of these are also true:\n\n- An attacker can start a device request: `validateClient` is not configured, or the attacker can use a valid public client.\n- Before allowing approval, your approval page does not show, from server-checked data, which client is asking and the exact permissions it requests.\n- Users may approve a code or complete verification link they did not start and cannot compare with a device they have.\n- Your application accepts the session token that the device flow returns, for example through the bearer plugin.\n\nYou are not affected if you do not enable the opt-in `deviceAuthorization()` plugin.\n\n## Summary\n\nThe device authorization plugin lets a user sign in on one device by approving a short code on another. In affected versions, the approval information given to the user leaves out which client asked for access and which permissions it wants. The official approval examples therefore show only a generic request and a code, s","public_affected_ranges":[">= 1.3.8-beta.3, < 1.7.0-rc.3"]},{"certainty":"source_listed","source_ids":["sr-8aa0a2040a7a7baccd6228c0f61d2df6"],"technology":"better-auth","known_exclusions":[],"conditions_summary":"## Am I affected?\n\nYou may be affected if you use `better-auth` from `1.3.8-beta.3` up to, but not including, `1.7.0-rc.3`, and you enable the `deviceAuthorization()` plugin. This range includes all 1.6 releases.\n\nYou are affected only if all of these are also true:\n\n- An attacker can start a device request: `validateClient` is not configured, or the attacker can use a valid public client.\n- Before allowing approval, your approval page does not show, from server-checked data, which client is asking and the exact permissions it requests.\n- Users may approve a code or complete verification link they did not start and cannot compare with a device they have.\n- Your application accepts the session token that the device flow returns, for example through the bearer plugin.\n\nYou are not affected if you do not enable the opt-in `deviceAuthorization()` plugin.\n\n## Summary\n\nThe device authorization plugin lets a user sign in on one device by approving a short code on another. In affected versions, the approval information given to the user leaves out which client asked for access and which permissions it wants. The official approval examples therefore show only a generic request and a code, s","public_affected_ranges":["SEMVER: introduced 1.3.8-beta.3; fixed 1.7.0-rc.3"]}],"null_published_at":"2026-11-07T18:43:12.080Z","source_updated_at":"2026-10-27T14:49:54.000Z","source_disclosed_at":"2026-10-27T14:49:53.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-31T22:06:46.371Z"},{"id":"NVI-00010722","kind":"vulnerability","title":"better-auth: Device login approval does not show the requesting client or permissions","revision":3,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-q84f-53jg-9ppm","CVE-2026-109346"],"plain_summary":"GitHub lists this reviewed advisory for better-auth. 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-02cd84d525b9e18c0afa69bc9274e228"],"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 1.7.0-rc.3 for better-auth. Confirm the publisher’s latest guidance.","source_ids":["sr-8aa0a2040a7a7baccd6228c0f61d2df6"],"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":[{"kind":"CVSS","as_of":"2026-10-27T14:49:54.000Z","value":"8.1 high","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-cdaefbeb4d60307bac0151ef3d5bcdaa"},{"kind":"EPSS","as_of":"2026-11-04T12:03:12.000Z","value":"0.278%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.20389. Missing scores are unknown.","source_id":"sr-02cd84d525b9e18c0afa69bc9274e228"}],"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-cdaefbeb4d60307bac0151ef3d5bcdaa","url":"https://github.com/advisories/GHSA-q84f-53jg-9ppm","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-q84f-53jg-9ppm","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T22:06:46.371Z"},{"id":"sr-8aa0a2040a7a7baccd6228c0f61d2df6","url":"https://github.com/advisories/GHSA-q84f-53jg-9ppm","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-q84f-53jg-9ppm","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-11-03T17:42:53.459Z"},{"id":"sr-02cd84d525b9e18c0afa69bc9274e228","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-109346","publisher":"FIRST EPSS","observed_at":"2026-11-04T17:58:50.311Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-cdaefbeb4d60307bac0151ef3d5bcdaa"],"technology":"better-auth","known_exclusions":[],"conditions_summary":"## Am I affected?\n\nYou may be affected if you use `better-auth` from `1.3.8-beta.3` up to, but not including, `1.7.0-rc.3`, and you enable the `deviceAuthorization()` plugin. This range includes all 1.6 releases.\n\nYou are affected only if all of these are also true:\n\n- An attacker can start a device request: `validateClient` is not configured, or the attacker can use a valid public client.\n- Before allowing approval, your approval page does not show, from server-checked data, which client is asking and the exact permissions it requests.\n- Users may approve a code or complete verification link they did not start and cannot compare with a device they have.\n- Your application accepts the session token that the device flow returns, for example through the bearer plugin.\n\nYou are not affected if you do not enable the opt-in `deviceAuthorization()` plugin.\n\n## Summary\n\nThe device authorization plugin lets a user sign in on one device by approving a short code on another. In affected versions, the approval information given to the user leaves out which client asked for access and which permissions it wants. The official approval examples therefore show only a generic request and a code, s","public_affected_ranges":[">= 1.3.8-beta.3, < 1.7.0-rc.3"]},{"certainty":"source_listed","source_ids":["sr-8aa0a2040a7a7baccd6228c0f61d2df6"],"technology":"better-auth","known_exclusions":[],"conditions_summary":"## Am I affected?\n\nYou may be affected if you use `better-auth` from `1.3.8-beta.3` up to, but not including, `1.7.0-rc.3`, and you enable the `deviceAuthorization()` plugin. This range includes all 1.6 releases.\n\nYou are affected only if all of these are also true:\n\n- An attacker can start a device request: `validateClient` is not configured, or the attacker can use a valid public client.\n- Before allowing approval, your approval page does not show, from server-checked data, which client is asking and the exact permissions it requests.\n- Users may approve a code or complete verification link they did not start and cannot compare with a device they have.\n- Your application accepts the session token that the device flow returns, for example through the bearer plugin.\n\nYou are not affected if you do not enable the opt-in `deviceAuthorization()` plugin.\n\n## Summary\n\nThe device authorization plugin lets a user sign in on one device by approving a short code on another. In affected versions, the approval information given to the user leaves out which client asked for access and which permissions it wants. The official approval examples therefore show only a generic request and a code, s","public_affected_ranges":["SEMVER: introduced 1.3.8-beta.3; fixed 1.7.0-rc.3"]}],"null_published_at":"2026-11-06T07:24:11.240Z","source_updated_at":"2026-10-27T14:49:54.000Z","source_disclosed_at":"2026-10-27T14:49:53.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-10-31T22:06:46.371Z"},{"id":"NVI-00010722","kind":"vulnerability","title":"better-auth: Device login approval does not show the requesting client or permissions","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-q84f-53jg-9ppm","CVE-2026-109346"],"plain_summary":"GitHub lists this reviewed advisory for better-auth. 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-cdaefbeb4d60307bac0151ef3d5bcdaa"],"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 1.7.0-rc.3 for better-auth. Confirm the publisher’s latest guidance.","source_ids":["sr-8aa0a2040a7a7baccd6228c0f61d2df6"],"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":[{"kind":"CVSS","as_of":"2026-10-27T14:49:54.000Z","value":"8.1 high","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-cdaefbeb4d60307bac0151ef3d5bcdaa"}],"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-cdaefbeb4d60307bac0151ef3d5bcdaa","url":"https://github.com/advisories/GHSA-q84f-53jg-9ppm","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-q84f-53jg-9ppm","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T22:06:46.371Z"},{"id":"sr-8aa0a2040a7a7baccd6228c0f61d2df6","url":"https://github.com/advisories/GHSA-q84f-53jg-9ppm","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-q84f-53jg-9ppm","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-11-03T17:42:53.459Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-cdaefbeb4d60307bac0151ef3d5bcdaa"],"technology":"better-auth","known_exclusions":[],"conditions_summary":"## Am I affected?\n\nYou may be affected if you use `better-auth` from `1.3.8-beta.3` up to, but not including, `1.7.0-rc.3`, and you enable the `deviceAuthorization()` plugin. This range includes all 1.6 releases.\n\nYou are affected only if all of these are also true:\n\n- An attacker can start a device request: `validateClient` is not configured, or the attacker can use a valid public client.\n- Before allowing approval, your approval page does not show, from server-checked data, which client is asking and the exact permissions it requests.\n- Users may approve a code or complete verification link they did not start and cannot compare with a device they have.\n- Your application accepts the session token that the device flow returns, for example through the bearer plugin.\n\nYou are not affected if you do not enable the opt-in `deviceAuthorization()` plugin.\n\n## Summary\n\nThe device authorization plugin lets a user sign in on one device by approving a short code on another. In affected versions, the approval information given to the user leaves out which client asked for access and which permissions it wants. The official approval examples therefore show only a generic request and a code, s","public_affected_ranges":[">= 1.3.8-beta.3, < 1.7.0-rc.3"]},{"certainty":"source_listed","source_ids":["sr-8aa0a2040a7a7baccd6228c0f61d2df6"],"technology":"better-auth","known_exclusions":[],"conditions_summary":"## Am I affected?\n\nYou may be affected if you use `better-auth` from `1.3.8-beta.3` up to, but not including, `1.7.0-rc.3`, and you enable the `deviceAuthorization()` plugin. This range includes all 1.6 releases.\n\nYou are affected only if all of these are also true:\n\n- An attacker can start a device request: `validateClient` is not configured, or the attacker can use a valid public client.\n- Before allowing approval, your approval page does not show, from server-checked data, which client is asking and the exact permissions it requests.\n- Users may approve a code or complete verification link they did not start and cannot compare with a device they have.\n- Your application accepts the session token that the device flow returns, for example through the bearer plugin.\n\nYou are not affected if you do not enable the opt-in `deviceAuthorization()` plugin.\n\n## Summary\n\nThe device authorization plugin lets a user sign in on one device by approving a short code on another. In affected versions, the approval information given to the user leaves out which client asked for access and which permissions it wants. The official approval examples therefore show only a generic request and a code, s","public_affected_ranges":["SEMVER: introduced 1.3.8-beta.3; fixed 1.7.0-rc.3"]}],"null_published_at":"2026-11-03T22:39:43.352Z","source_updated_at":"2026-10-27T14:49:54.000Z","source_disclosed_at":"2026-10-27T14:49:53.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-31T22:06:46.371Z"},{"id":"NVI-00010722","kind":"vulnerability","title":"better-auth: Device login approval does not show the requesting client or permissions","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-q84f-53jg-9ppm"],"plain_summary":"GitHub lists this reviewed advisory for better-auth. 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-cdaefbeb4d60307bac0151ef3d5bcdaa"],"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-10-27T14:49:54.000Z","value":"8.1 high","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-cdaefbeb4d60307bac0151ef3d5bcdaa"}],"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-cdaefbeb4d60307bac0151ef3d5bcdaa","url":"https://github.com/advisories/GHSA-q84f-53jg-9ppm","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-q84f-53jg-9ppm","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T22:06:46.371Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-cdaefbeb4d60307bac0151ef3d5bcdaa"],"technology":"better-auth","known_exclusions":[],"conditions_summary":"## Am I affected?\n\nYou may be affected if you use `better-auth` from `1.3.8-beta.3` up to, but not including, `1.7.0-rc.3`, and you enable the `deviceAuthorization()` plugin. This range includes all 1.6 releases.\n\nYou are affected only if all of these are also true:\n\n- An attacker can start a device request: `validateClient` is not configured, or the attacker can use a valid public client.\n- Before allowing approval, your approval page does not show, from server-checked data, which client is asking and the exact permissions it requests.\n- Users may approve a code or complete verification link they did not start and cannot compare with a device they have.\n- Your application accepts the session token that the device flow returns, for example through the bearer plugin.\n\nYou are not affected if you do not enable the opt-in `deviceAuthorization()` plugin.\n\n## Summary\n\nThe device authorization plugin lets a user sign in on one device by approving a short code on another. In affected versions, the approval information given to the user leaves out which client asked for access and which permissions it wants. The official approval examples therefore show only a generic request and a code, s","public_affected_ranges":[">= 1.3.8-beta.3, < 1.7.0-rc.3"]}],"null_published_at":"2026-10-31T22:27:12.377Z","source_updated_at":"2026-10-27T14:49:54.000Z","source_disclosed_at":"2026-10-27T14:49:53.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-31T22:06:46.371Z"}],"next_cursor":null,"snapshot_revision":"42594"}