{"as_of":"2026-08-15T23:34:00Z","caps":{"database_statements":6,"inbound":100,"outbound":100},"context_digest":"sha256:568350f4b7ef8b6a279a1e89659ec442c7a9e9046c6c66796f440d3ab2b4bde2","coverage":[{"denominator":0,"lane":"reference_resolution","note":"Typed states for the displayed outbound observations.","records_observed":0,"source":"paper_references, paper_reference_links","source_observed_at":null,"state":"measured"},{"denominator":5,"lane":"standing_notices","note":"One-hop event checks from named stored sources.","records_observed":5,"source":"scholarly_work_events, retraction_status_cache","source_observed_at":"2026-08-15T06:32:42.880941+00:00","state":"measured"},{"denominator":5,"lane":"inbound_itemization","note":"Pith citing papers itemized under the disclosed page cap.","records_observed":5,"source":"paper_references, paper_reference_links","source_observed_at":"2026-08-09T12:47:21.670033Z","state":"measured"},{"denominator":1,"lane":"external_citation_measurements","note":"A source-named dated measurement, never combined with another source.","records_observed":0,"source":"arxiv_reference","source_observed_at":"2026-05-19T10:32:14.773793Z","state":"measured"}],"external_citation_measurements":[],"inbound":[{"citation":{"cited_paper":{"arxiv_id":"2407.02551","last_updated":"2024-10-30T17:16:44Z","snapshot_observed_at":"2026-08-12T23:30:16.785484Z","submitted_at":"2024-07-02T16:19:25Z","title":"Breach By A Thousand Leaks: Unsafe Information Leakage in `Safe' AI Responses","version":2},"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":"2407.02551","snapshot_observed_at":"2026-08-09T12:47:21.670033Z","title":"Breach by a thousand leaks: Unsafe information leakage insafe’ai responses","venue":null,"work_id":null,"year":null},"citing_paper":{"arxiv_id":"2502.02260","last_updated":"2026-06-02T17:48:48Z","snapshot_observed_at":"2026-08-12T14:47:41.023865Z","submitted_at":"2025-02-04T12:17:08Z","title":"Position: Adversarial ML for LLMs Is Not Making Any Progress","version":2},"reference_index":22,"source":"pdf_text","source_observed_at":"2026-08-09T12:47:21.670033Z"},"links":{"cited_paper":"/paper/2407.02551","citing_paper":"/paper/2502.02260"},"observation_digest":"sha256:20ef5f67459b96e8a443504f11849d26dcca264b5211e1edf00f64a9caca9825","observation_id":"25e8cd30-8d47-46a1-8a3d-3b7220e4fa23","resolution":{"observed_at":"2026-08-09T12:47:21.670033Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":{"arxiv_id":"2407.02551","last_updated":"2024-10-30T17:16:44Z","snapshot_observed_at":"2026-08-12T23:30:16.785484Z","submitted_at":"2024-07-02T16:19:25Z","title":"Breach By A Thousand Leaks: Unsafe Information Leakage in `Safe' AI Responses","version":2},"cited_work":{"arxiv_id":"2407.02551","doi":null,"metadata_source":"arxiv_reference","pith_arxiv_id":"2407.02551","snapshot_observed_at":"2026-06-05T21:23:00.469572Z","title":"Breach by a thousand leaks: Unsafe information leakage in ‘safe’ ai responses.arXiv preprint arXiv: 2407.02551","venue":null,"work_id":"c39d6391-aae2-4002-84b9-6ee3b1809189","year":2024},"citing_paper":{"arxiv_id":"2506.06414","last_updated":"2026-04-20T20:58:30Z","snapshot_observed_at":"2026-08-10T17:13:42.931667Z","submitted_at":"2025-06-06T17:33:33Z","title":"Benchmarking Misuse Mitigation Against Covert Adversaries","version":2},"reference_index":19,"source":"pdf_text","source_observed_at":"2026-05-19T10:29:05.104520Z"},"links":{"cited_paper":"/paper/2407.02551","citing_paper":"/paper/2506.06414"},"observation_digest":"sha256:64f74e213a6abc79ac32d364c5d36c50a684de9d56f1f573384b14926cfc8a98","observation_id":"10f8b811-0254-4319-9964-7d2beae0018a","resolution":{"observed_at":"2026-05-19T10:32:14.775623Z","resolver_source":"arxiv_id","status":"verified_exact"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-15T06:32:42.880941+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-15T06:32:42.880941+00:00","source":"crossref"},{"observed_at":"2026-08-15T06:32:39.529945+00:00","source":"retraction_watch"}],"state":"measured"}},{"citation":{"cited_paper":{"arxiv_id":"2407.02551","last_updated":"2024-10-30T17:16:44Z","snapshot_observed_at":"2026-08-12T23:30:16.785484Z","submitted_at":"2024-07-02T16:19:25Z","title":"Breach By A Thousand Leaks: Unsafe Information Leakage in `Safe' AI Responses","version":2},"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":"2407.02551","snapshot_observed_at":"2026-08-04T09:25:41.056143Z","title":"A false sense of safety: Unsafe information leakage in ’safe’ AI responses.CoRR, abs/2407.02551, 2024","venue":null,"work_id":null,"year":2024},"citing_paper":{"arxiv_id":"2510.15476","last_updated":"2026-07-04T04:20:15Z","snapshot_observed_at":"2026-08-14T22:20:04.981358Z","submitted_at":"2025-10-17T09:38:54Z","title":"SoK: Systematizing LLM Prompt Security: Taxonomies, Datasets, and Unified Evaluation of Attacks and Defenses","version":3},"reference_index":60,"source":"pdf_text","source_observed_at":"2026-08-04T09:25:41.056143Z"},"links":{"cited_paper":"/paper/2407.02551","citing_paper":"/paper/2510.15476"},"observation_digest":"sha256:1d88bc8be354d33f6cf4594fc42bdb128510e8033738dbdef223c6e7690abd59","observation_id":"dcd95c5d-ffb9-484a-b7fc-9d929a2e496a","resolution":{"observed_at":"2026-08-04T09:25:41.056143Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":{"arxiv_id":"2407.02551","last_updated":"2024-10-30T17:16:44Z","snapshot_observed_at":"2026-08-12T23:30:16.785484Z","submitted_at":"2024-07-02T16:19:25Z","title":"Breach By A Thousand Leaks: Unsafe Information Leakage in `Safe' AI Responses","version":2},"cited_work":{"arxiv_id":"2407.02551","doi":null,"metadata_source":"arxiv_reference","pith_arxiv_id":"2407.02551","snapshot_observed_at":"2026-06-05T21:23:00.469572Z","title":"Breach by a thousand leaks: Unsafe information leakage in ‘safe’ ai responses.arXiv preprint arXiv: 2407.02551","venue":null,"work_id":"c39d6391-aae2-4002-84b9-6ee3b1809189","year":2024},"citing_paper":{"arxiv_id":"2604.21131","last_updated":"2026-04-22T22:40:31Z","snapshot_observed_at":"2026-07-06T23:07:47.244208Z","submitted_at":"2026-04-22T22:40:31Z","title":"Cross-Session Threats in AI Agents: Benchmark, Evaluation, and Algorithms","version":1},"reference_index":12,"source":"pdf_text","source_observed_at":"2026-05-09T23:44:44.036643Z"},"links":{"cited_paper":"/paper/2407.02551","citing_paper":"/paper/2604.21131"},"observation_digest":"sha256:425424ea85e85dc91cbe9f27a155c7acd01007b1fd23e6e281332cc7b47e8f21","observation_id":"c5b9060d-406a-42a1-a836-973c8ef463cf","resolution":{"observed_at":"2026-05-11T14:01:06.443389Z","resolver_source":"arxiv_id","status":"verified_exact"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-15T06:32:42.880941+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-15T06:32:42.880941+00:00","source":"crossref"},{"observed_at":"2026-08-15T06:32:39.529945+00:00","source":"retraction_watch"}],"state":"measured"}},{"citation":{"cited_paper":{"arxiv_id":"2407.02551","last_updated":"2024-10-30T17:16:44Z","snapshot_observed_at":"2026-08-12T23:30:16.785484Z","submitted_at":"2024-07-02T16:19:25Z","title":"Breach By A Thousand Leaks: Unsafe Information Leakage in `Safe' AI Responses","version":2},"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":"2407.02551","snapshot_observed_at":"2026-07-31T22:25:22.240902Z","title":"arXiv preprint arXiv:2407.02551 , year =","venue":null,"work_id":null,"year":null},"citing_paper":{"arxiv_id":"2607.27951","last_updated":"2026-07-30T09:59:08Z","snapshot_observed_at":"2026-08-15T17:44:46.059265Z","submitted_at":"2026-07-30T09:59:08Z","title":"Safeguards Based on Copyable Context Cannot Provide Reliable Safety for LLMs","version":1},"reference_index":16,"source":"arxiv_source","source_observed_at":"2026-07-31T22:25:22.240902Z"},"links":{"cited_paper":"/paper/2407.02551","citing_paper":"/paper/2607.27951"},"observation_digest":"sha256:2085b1a6f764072259a3be70c916625a4c868b5825b9ccfb17f52370d7b889e7","observation_id":"b26dd81b-395d-4418-a466-aaa50b355dc4","resolution":{"observed_at":"2026-07-31T22:25:22.240902Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}}],"links":{"evidence":"/evidence","html":"/paper/2407.02551/citation-record","integrity":"/paper/2407.02551/integrity","json":"/paper/2407.02551/citation-record.json","paper":"/paper/2407.02551"},"outbound":[],"paper":{"arxiv_id":"2407.02551","last_updated":"2024-10-30T17:16:44Z","latest_version":2,"primary_category":"cs.CR","snapshot_observed_at":"2026-08-12T23:30:16.785484Z","submitted_at":"2024-07-02T16:19:25Z","title":"Breach By A Thousand Leaks: Unsafe Information Leakage in `Safe' AI Responses"},"reference_resolution":{"displayed":0,"state_counts":{"malformed_identifier":0,"metadata_mismatch":0,"parse_uncertain":0,"unresolved":0,"verified_exact":0,"verified_fuzzy":0},"total_outbound_references":0},"refusal":"A citation records a reference. It does not transfer a finding from one paper to another.","schema":"pith.paper-citation-record.v1","standing_sources":[{"observed_at":"2026-08-15T06:32:42.880941+00:00","source":"crossref"},{"observed_at":"2026-08-15T06:32:39.529945+00:00","source":"retraction_watch"}],"thesis":"As of 15 August 2026, this Paper Citation Record lists 0 of 0 outbound references and 5 inbound Pith citation observations for arXiv:2407.02551."}