Record · corpus.blog/posts/01a0879a-e0df-70eb-93e3-4e4f2ed59a99

Probes arrived 10 minutes after the cohttp path traversal fix PR went public

lilting.ch · published 30 August 2026

A record is what was published and who pointed at it. The text of the post is not held here: read it at the source, or at its Wayback capture.

Read the post at lilting.ch Wayback capture

0blogs citing

First cited: —
Most recent: —
Rank this month: not ranked
Links from this post: 19
Words captured: 2,260

Cited by

No blog we hold has cited this post yet.

Links from this post

Link

Host

https://lilting.ch/en/articles/ffmpeg-21-zero-days-av1-rtp-poc

lilting.ch

https://lilting.ch/en/articles/claude-mythos-project-glasswing-zero-day

lilting.ch

https://lilting.ch/en/articles/claude-fable-mythos-export-control-suspension

lilting.ch

Just a rumour of a bug is enough to find a security exploit these days Read at the source ↗

anil.recoil.org

https://osv.dev/vulnerability/OSEC-2026-16

osv.dev

https://github.com/mirage/ocaml-cohttp/pull/1145

github.com

https://arxiv.org/abs/2404.08144

arxiv.org

https://cloud.google.com/blog/topics/threat-intelligence/m-trends-2026

cloud.google.com

https://cloud.google.com/blog/topics/threat-intelligence/time-to-exploit-trends-2023

cloud.google.com

https://www.sysdig.com/blog/marimo-oss-python-notebook-rce-from-disclosure-to-exploitation-in-under-10-hours

sysdig.com

https://www.sysdig.com/blog/cve-2026-33017-how-attackers-compromised-langflow-ai-pipelines-in-20-hours

sysdig.com

VulnCheck State of Exploitation 1H-2026 Read at the source ↗

vulncheck.com

https://red.anthropic.com/2026/cvd/

red.anthropic.com

https://www.anthropic.com/news/expanding-project-glasswing

anthropic.com

https://arxiv.org/abs/2605.24632

arxiv.org

https://docs.github.com/en/code-security/tutorials/fix-reported-vulnerabilities/collaborate-in-a-fork

docs.github.com

https://blog.google/security/chrome-stronger-with-every-update/

blog.google

https://docs.kernel.org/process/security-bugs.html

docs.kernel.org

https://blog.cloudflare.com/how-cloudflare-security-responded-to-log4j2-vulnerability/

blog.cloudflare.com