{"items":[{"id":"NVI-00011831","kind":"vulnerability","title":"Quasar Framework: Development TLS private keys are cached with overly permissive filesystem 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-fh39-c73x-5pjv","CVE-2026-106105"],"plain_summary":"GitHub lists this reviewed advisory for @quasar/ssl-certificate, @quasar/cli, @quasar/app-vite. 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-0e77df9b891c6a3c61a9016bd48ef9d0"],"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-06T20:03:40.690Z","value":"8.4 HIGH (4.0)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-568e4bd4d3739aeb27df55551f21530f"},{"kind":"EPSS","as_of":"2026-11-04T12:03:12.000Z","value":"0.068%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.00027. Missing scores are unknown.","source_id":"sr-0e77df9b891c6a3c61a9016bd48ef9d0"}],"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-3db69446ca5cc7bab02fc784aee92a8c","url":"https://github.com/advisories/GHSA-fh39-c73x-5pjv","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-fh39-c73x-5pjv","publisher":"GitHub Advisory Database","observed_at":"2026-11-01T00:58:46.232Z"},{"id":"sr-568e4bd4d3739aeb27df55551f21530f","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-106105","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-106105","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-03T09:58:21.903Z"},{"id":"sr-0e77df9b891c6a3c61a9016bd48ef9d0","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-106105","publisher":"FIRST EPSS","observed_at":"2026-11-04T17:58:50.309Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-3db69446ca5cc7bab02fc784aee92a8c"],"technology":"@quasar/ssl-certificate","known_exclusions":[],"conditions_summary":"The `@quasar/ssl-certificate` development utility caches a combined PEM containing a generated private key and certificate without explicitly restricting its filesystem permissions. On systems with a typical process umask, the PEM can be readable by other local users. A local attacker with filesystem access could copy and reuse the private key to impersonate a development TLS endpoint in an environment that trusts the certificate.\n\nThe generated certificate was also unnecessarily CA-capable and included broad key usages beyond its localhost HTTPS purpose. Its IPv6 loopback entry was encoded as a DNS name rather than an IP subject alternative name.\n\nThe remediation writes and repairs the cached PEM with owner-only permissions on supported platforms, generates a non-CA server-auth leaf certificate with constrained key usage, corrects the IPv6 loopback SAN, and bases cache expiry on content modification time so permission metadata changes cannot extend the certificate lifetime. This issue does not expose the key remotely by itself; exploitation requires another local user to be able to read the cached PEM file.","public_affected_ranges":["<= 2.0.0"]},{"certainty":"source_listed","source_ids":["sr-3db69446ca5cc7bab02fc784aee92a8c"],"technology":"@quasar/cli","known_exclusions":[],"conditions_summary":"The `@quasar/ssl-certificate` development utility caches a combined PEM containing a generated private key and certificate without explicitly restricting its filesystem permissions. On systems with a typical process umask, the PEM can be readable by other local users. A local attacker with filesystem access could copy and reuse the private key to impersonate a development TLS endpoint in an environment that trusts the certificate.\n\nThe generated certificate was also unnecessarily CA-capable and included broad key usages beyond its localhost HTTPS purpose. Its IPv6 loopback entry was encoded as a DNS name rather than an IP subject alternative name.\n\nThe remediation writes and repairs the cached PEM with owner-only permissions on supported platforms, generates a non-CA server-auth leaf certificate with constrained key usage, corrects the IPv6 loopback SAN, and bases cache expiry on content modification time so permission metadata changes cannot extend the certificate lifetime. This issue does not expose the key remotely by itself; exploitation requires another local user to be able to read the cached PEM file.","public_affected_ranges":["<= 5.0.3"]},{"certainty":"source_listed","source_ids":["sr-3db69446ca5cc7bab02fc784aee92a8c"],"technology":"@quasar/app-vite","known_exclusions":[],"conditions_summary":"The `@quasar/ssl-certificate` development utility caches a combined PEM containing a generated private key and certificate without explicitly restricting its filesystem permissions. On systems with a typical process umask, the PEM can be readable by other local users. A local attacker with filesystem access could copy and reuse the private key to impersonate a development TLS endpoint in an environment that trusts the certificate.\n\nThe generated certificate was also unnecessarily CA-capable and included broad key usages beyond its localhost HTTPS purpose. Its IPv6 loopback entry was encoded as a DNS name rather than an IP subject alternative name.\n\nThe remediation writes and repairs the cached PEM with owner-only permissions on supported platforms, generates a non-CA server-auth leaf certificate with constrained key usage, corrects the IPv6 loopback SAN, and bases cache expiry on content modification time so permission metadata changes cannot extend the certificate lifetime. This issue does not expose the key remotely by itself; exploitation requires another local user to be able to read the cached PEM file.","public_affected_ranges":["<= 3.2.0"]}],"null_published_at":"2026-11-07T14:02:01.388Z","source_updated_at":"2026-10-07T16:16:19.000Z","source_disclosed_at":"2026-10-07T16:16:18.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-01T00:58:46.232Z"},{"id":"NVI-00011831","kind":"vulnerability","title":"Quasar Framework: Development TLS private keys are cached with overly permissive filesystem permissions","revision":3,"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-fh39-c73x-5pjv","CVE-2026-106105"],"plain_summary":"GitHub lists this reviewed advisory for @quasar/ssl-certificate, @quasar/cli, @quasar/app-vite. 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-4874f18d5acdd420d4f4c98866b65177"],"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-06T20:03:40.690Z","value":"8.4 HIGH (4.0)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-568e4bd4d3739aeb27df55551f21530f"},{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.068%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.00027. Missing scores are unknown.","source_id":"sr-4874f18d5acdd420d4f4c98866b65177"}],"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-3db69446ca5cc7bab02fc784aee92a8c","url":"https://github.com/advisories/GHSA-fh39-c73x-5pjv","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-fh39-c73x-5pjv","publisher":"GitHub Advisory Database","observed_at":"2026-11-01T00:58:46.232Z"},{"id":"sr-568e4bd4d3739aeb27df55551f21530f","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-106105","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-106105","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-03T09:58:21.903Z"},{"id":"sr-4874f18d5acdd420d4f4c98866b65177","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-106105","publisher":"FIRST EPSS","observed_at":"2026-11-01T01:39:43.064Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-3db69446ca5cc7bab02fc784aee92a8c"],"technology":"@quasar/ssl-certificate","known_exclusions":[],"conditions_summary":"The `@quasar/ssl-certificate` development utility caches a combined PEM containing a generated private key and certificate without explicitly restricting its filesystem permissions. On systems with a typical process umask, the PEM can be readable by other local users. A local attacker with filesystem access could copy and reuse the private key to impersonate a development TLS endpoint in an environment that trusts the certificate.\n\nThe generated certificate was also unnecessarily CA-capable and included broad key usages beyond its localhost HTTPS purpose. Its IPv6 loopback entry was encoded as a DNS name rather than an IP subject alternative name.\n\nThe remediation writes and repairs the cached PEM with owner-only permissions on supported platforms, generates a non-CA server-auth leaf certificate with constrained key usage, corrects the IPv6 loopback SAN, and bases cache expiry on content modification time so permission metadata changes cannot extend the certificate lifetime. This issue does not expose the key remotely by itself; exploitation requires another local user to be able to read the cached PEM file.","public_affected_ranges":["<= 2.0.0"]},{"certainty":"source_listed","source_ids":["sr-3db69446ca5cc7bab02fc784aee92a8c"],"technology":"@quasar/cli","known_exclusions":[],"conditions_summary":"The `@quasar/ssl-certificate` development utility caches a combined PEM containing a generated private key and certificate without explicitly restricting its filesystem permissions. On systems with a typical process umask, the PEM can be readable by other local users. A local attacker with filesystem access could copy and reuse the private key to impersonate a development TLS endpoint in an environment that trusts the certificate.\n\nThe generated certificate was also unnecessarily CA-capable and included broad key usages beyond its localhost HTTPS purpose. Its IPv6 loopback entry was encoded as a DNS name rather than an IP subject alternative name.\n\nThe remediation writes and repairs the cached PEM with owner-only permissions on supported platforms, generates a non-CA server-auth leaf certificate with constrained key usage, corrects the IPv6 loopback SAN, and bases cache expiry on content modification time so permission metadata changes cannot extend the certificate lifetime. This issue does not expose the key remotely by itself; exploitation requires another local user to be able to read the cached PEM file.","public_affected_ranges":["<= 5.0.3"]},{"certainty":"source_listed","source_ids":["sr-3db69446ca5cc7bab02fc784aee92a8c"],"technology":"@quasar/app-vite","known_exclusions":[],"conditions_summary":"The `@quasar/ssl-certificate` development utility caches a combined PEM containing a generated private key and certificate without explicitly restricting its filesystem permissions. On systems with a typical process umask, the PEM can be readable by other local users. A local attacker with filesystem access could copy and reuse the private key to impersonate a development TLS endpoint in an environment that trusts the certificate.\n\nThe generated certificate was also unnecessarily CA-capable and included broad key usages beyond its localhost HTTPS purpose. Its IPv6 loopback entry was encoded as a DNS name rather than an IP subject alternative name.\n\nThe remediation writes and repairs the cached PEM with owner-only permissions on supported platforms, generates a non-CA server-auth leaf certificate with constrained key usage, corrects the IPv6 loopback SAN, and bases cache expiry on content modification time so permission metadata changes cannot extend the certificate lifetime. This issue does not expose the key remotely by itself; exploitation requires another local user to be able to read the cached PEM file.","public_affected_ranges":["<= 3.2.0"]}],"null_published_at":"2026-11-05T19:10:23.275Z","source_updated_at":"2026-10-07T16:16:19.000Z","source_disclosed_at":"2026-10-07T16:16:18.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-11-01T00:58:46.232Z"},{"id":"NVI-00011831","kind":"vulnerability","title":"Quasar Framework: Development TLS private keys are cached with overly permissive filesystem permissions","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-fh39-c73x-5pjv","CVE-2026-106105"],"plain_summary":"GitHub lists this reviewed advisory for @quasar/ssl-certificate, @quasar/cli, @quasar/app-vite. 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-4874f18d5acdd420d4f4c98866b65177"],"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":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.068%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.00027. Missing scores are unknown.","source_id":"sr-4874f18d5acdd420d4f4c98866b65177"}],"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-3db69446ca5cc7bab02fc784aee92a8c","url":"https://github.com/advisories/GHSA-fh39-c73x-5pjv","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-fh39-c73x-5pjv","publisher":"GitHub Advisory Database","observed_at":"2026-11-01T00:58:46.232Z"},{"id":"sr-4874f18d5acdd420d4f4c98866b65177","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-106105","publisher":"FIRST EPSS","observed_at":"2026-11-01T01:39:43.064Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-3db69446ca5cc7bab02fc784aee92a8c"],"technology":"@quasar/ssl-certificate","known_exclusions":[],"conditions_summary":"The `@quasar/ssl-certificate` development utility caches a combined PEM containing a generated private key and certificate without explicitly restricting its filesystem permissions. On systems with a typical process umask, the PEM can be readable by other local users. A local attacker with filesystem access could copy and reuse the private key to impersonate a development TLS endpoint in an environment that trusts the certificate.\n\nThe generated certificate was also unnecessarily CA-capable and included broad key usages beyond its localhost HTTPS purpose. Its IPv6 loopback entry was encoded as a DNS name rather than an IP subject alternative name.\n\nThe remediation writes and repairs the cached PEM with owner-only permissions on supported platforms, generates a non-CA server-auth leaf certificate with constrained key usage, corrects the IPv6 loopback SAN, and bases cache expiry on content modification time so permission metadata changes cannot extend the certificate lifetime. This issue does not expose the key remotely by itself; exploitation requires another local user to be able to read the cached PEM file.","public_affected_ranges":["<= 2.0.0"]},{"certainty":"source_listed","source_ids":["sr-3db69446ca5cc7bab02fc784aee92a8c"],"technology":"@quasar/cli","known_exclusions":[],"conditions_summary":"The `@quasar/ssl-certificate` development utility caches a combined PEM containing a generated private key and certificate without explicitly restricting its filesystem permissions. On systems with a typical process umask, the PEM can be readable by other local users. A local attacker with filesystem access could copy and reuse the private key to impersonate a development TLS endpoint in an environment that trusts the certificate.\n\nThe generated certificate was also unnecessarily CA-capable and included broad key usages beyond its localhost HTTPS purpose. Its IPv6 loopback entry was encoded as a DNS name rather than an IP subject alternative name.\n\nThe remediation writes and repairs the cached PEM with owner-only permissions on supported platforms, generates a non-CA server-auth leaf certificate with constrained key usage, corrects the IPv6 loopback SAN, and bases cache expiry on content modification time so permission metadata changes cannot extend the certificate lifetime. This issue does not expose the key remotely by itself; exploitation requires another local user to be able to read the cached PEM file.","public_affected_ranges":["<= 5.0.3"]},{"certainty":"source_listed","source_ids":["sr-3db69446ca5cc7bab02fc784aee92a8c"],"technology":"@quasar/app-vite","known_exclusions":[],"conditions_summary":"The `@quasar/ssl-certificate` development utility caches a combined PEM containing a generated private key and certificate without explicitly restricting its filesystem permissions. On systems with a typical process umask, the PEM can be readable by other local users. A local attacker with filesystem access could copy and reuse the private key to impersonate a development TLS endpoint in an environment that trusts the certificate.\n\nThe generated certificate was also unnecessarily CA-capable and included broad key usages beyond its localhost HTTPS purpose. Its IPv6 loopback entry was encoded as a DNS name rather than an IP subject alternative name.\n\nThe remediation writes and repairs the cached PEM with owner-only permissions on supported platforms, generates a non-CA server-auth leaf certificate with constrained key usage, corrects the IPv6 loopback SAN, and bases cache expiry on content modification time so permission metadata changes cannot extend the certificate lifetime. This issue does not expose the key remotely by itself; exploitation requires another local user to be able to read the cached PEM file.","public_affected_ranges":["<= 3.2.0"]}],"null_published_at":"2026-11-01T22:58:19.124Z","source_updated_at":"2026-10-07T16:16:19.000Z","source_disclosed_at":"2026-10-07T16:16:18.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-01T00:58:46.232Z"},{"id":"NVI-00011831","kind":"vulnerability","title":"Quasar Framework: Development TLS private keys are cached with overly permissive filesystem permissions","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-fh39-c73x-5pjv","CVE-2026-106105"],"plain_summary":"GitHub lists this reviewed advisory for @quasar/ssl-certificate, @quasar/cli, @quasar/app-vite. 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-3db69446ca5cc7bab02fc784aee92a8c"],"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":[],"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-3db69446ca5cc7bab02fc784aee92a8c","url":"https://github.com/advisories/GHSA-fh39-c73x-5pjv","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-fh39-c73x-5pjv","publisher":"GitHub Advisory Database","observed_at":"2026-11-01T00:58:46.232Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-3db69446ca5cc7bab02fc784aee92a8c"],"technology":"@quasar/ssl-certificate","known_exclusions":[],"conditions_summary":"The `@quasar/ssl-certificate` development utility caches a combined PEM containing a generated private key and certificate without explicitly restricting its filesystem permissions. On systems with a typical process umask, the PEM can be readable by other local users. A local attacker with filesystem access could copy and reuse the private key to impersonate a development TLS endpoint in an environment that trusts the certificate.\n\nThe generated certificate was also unnecessarily CA-capable and included broad key usages beyond its localhost HTTPS purpose. Its IPv6 loopback entry was encoded as a DNS name rather than an IP subject alternative name.\n\nThe remediation writes and repairs the cached PEM with owner-only permissions on supported platforms, generates a non-CA server-auth leaf certificate with constrained key usage, corrects the IPv6 loopback SAN, and bases cache expiry on content modification time so permission metadata changes cannot extend the certificate lifetime. This issue does not expose the key remotely by itself; exploitation requires another local user to be able to read the cached PEM file.","public_affected_ranges":["<= 2.0.0"]},{"certainty":"source_listed","source_ids":["sr-3db69446ca5cc7bab02fc784aee92a8c"],"technology":"@quasar/cli","known_exclusions":[],"conditions_summary":"The `@quasar/ssl-certificate` development utility caches a combined PEM containing a generated private key and certificate without explicitly restricting its filesystem permissions. On systems with a typical process umask, the PEM can be readable by other local users. A local attacker with filesystem access could copy and reuse the private key to impersonate a development TLS endpoint in an environment that trusts the certificate.\n\nThe generated certificate was also unnecessarily CA-capable and included broad key usages beyond its localhost HTTPS purpose. Its IPv6 loopback entry was encoded as a DNS name rather than an IP subject alternative name.\n\nThe remediation writes and repairs the cached PEM with owner-only permissions on supported platforms, generates a non-CA server-auth leaf certificate with constrained key usage, corrects the IPv6 loopback SAN, and bases cache expiry on content modification time so permission metadata changes cannot extend the certificate lifetime. This issue does not expose the key remotely by itself; exploitation requires another local user to be able to read the cached PEM file.","public_affected_ranges":["<= 5.0.3"]},{"certainty":"source_listed","source_ids":["sr-3db69446ca5cc7bab02fc784aee92a8c"],"technology":"@quasar/app-vite","known_exclusions":[],"conditions_summary":"The `@quasar/ssl-certificate` development utility caches a combined PEM containing a generated private key and certificate without explicitly restricting its filesystem permissions. On systems with a typical process umask, the PEM can be readable by other local users. A local attacker with filesystem access could copy and reuse the private key to impersonate a development TLS endpoint in an environment that trusts the certificate.\n\nThe generated certificate was also unnecessarily CA-capable and included broad key usages beyond its localhost HTTPS purpose. Its IPv6 loopback entry was encoded as a DNS name rather than an IP subject alternative name.\n\nThe remediation writes and repairs the cached PEM with owner-only permissions on supported platforms, generates a non-CA server-auth leaf certificate with constrained key usage, corrects the IPv6 loopback SAN, and bases cache expiry on content modification time so permission metadata changes cannot extend the certificate lifetime. This issue does not expose the key remotely by itself; exploitation requires another local user to be able to read the cached PEM file.","public_affected_ranges":["<= 3.2.0"]}],"null_published_at":"2026-11-01T01:03:56.608Z","source_updated_at":"2026-10-07T16:16:19.000Z","source_disclosed_at":"2026-10-07T16:16:18.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-01T00:58:46.232Z"}],"next_cursor":null,"snapshot_revision":"42594"}