• News/
  • https://www.theregister.com/2025/06/05/llm_kept_persistent_path_traversal_bug_alive/

AI kept 15-year-old zombie vuln alive, but its time is drawing near

The Register
·
Thomas Claburn
·
Published Jun 5, 2025
·
Updated

A security bug that surfaced fifteen years ago in a public post on GitHub has survived developers' attempts on its life. Despite multiple developer warnings about the 2010 GitHub Gist containing the path traversal vulnerability in 2012, 2014, and 2018, the flaw appeared in MDN Web Docs documentation and a Stack Overflow snippet. From there, it took up residence in large language models (LLMs) trained on the flawed examples. But its days may be numbered. "The vulnerable code snippet was found first in 2010 in a GitHub Gist, and it spread to Stack Overflow, famous companies, tutorials, and even university courses," Jafar Akhoundali, a PhD candidate from Leiden University in The Netherlands, told The Register in an email. It even contaminated LLMs and made them produce mostly insecure code when asked to write code for this task "Most people failed to point out it's vulnerable, and although the vulnerability is simple, some small details prevented most users from seeing the vulnerability. It even contaminated LLMs and made them produce mostly insecure code when asked to write code for this task." Akhoundali, who contributed to a 2019 research paper about the risks of copying and pasting from Stack Overflow examples, aims to exterminate the bug with an automated vulnerability repair system. Akhoundali and co-authors Hamidreza Hamidi, Kristian Rietveld, and Olga Gadyatskaya describe how they're doing so in a preprint paper titled "Eradicating the Unseen: Detecting, Exploiting, and ...

Read full article

Affected Software

3 affected components
GitHub Gist
GitHub Gist
MDN Web Docs
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the main topic of this article?

The article discusses a persistent path traversal vulnerability that has remained unresolved for 15 years due to a public GitHub post.

2

What security implications are discussed in this article?

The security implications include the ongoing risks associated with an old vulnerability that continues to exist despite multiple warnings from developers.

3

What software is primarily affected by the vulnerability mentioned?

The primary software affected by the vulnerability is GitHub Gist.

4

How was the vulnerability discovered?

The vulnerability was publicly disclosed in a GitHub Gist back in 2010 and has been continuously documented since.

5

What advancements in AI are mentioned in the article regarding this vulnerability?

The article highlights how AI technologies have recognized and kept the discussion around the long-standing vulnerability alive.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203