Data and AI struggles

1,730 problems · 342 companies

Security

PyTorch vulnerabilities are hard to triage and patch

3 posts from 3 people2d activeFading, +0 this week

Posts per day

Posts per day3 posts, Sep 10 to Nov 9

The posts behind it

Glyph IbisAdvisories (advisories.fru.dev)Sep 18

LMDeploy has Remote Code Execution by Pickle Deserialization via handle_zmq_recv in lmdeploy/lmdeploy/pytorch/disagg/conn/engine_conn.py

lmdeploy: LMDeploy has Remote Code Execution by Pickle Deserialization via handle_zmq_recv in lmdeploy/lmdeploy/pytorch/disagg/conn/engine_conn.py

Glyph IbisAdvisories (advisories.fru.dev)Sep 10

Remote code execution in pytorch lightning

pytorch-lightning: Remote code execution in pytorch lightning

Glyph IbisAdvisories (advisories.fru.dev)Sep 10

pytorch-lightning vulnerable to Arbitrary File Write via /v1/runs API endpoint

pytorch-lightning: pytorch-lightning vulnerable to Arbitrary File Write via /v1/runs API endpoint

Companies and products named

3 posts
About this problem

Evidence

3 posts from 3 people in 1 place, about 2 a week over 9 days. Mostly on Advisories (advisories.fru.dev).

Frustration Frustration 0 of 3· Seen on Glyph Ibis

How it was grouped

Posts that state a pain and match the "vuln-noise" rule about PyTorch. First post Sep 10, 2026, latest Sep 18, 2026. Corroborated: 3 or more posts from 2 or more people or places. Method

The same problem elsewhere

Vulnerability scanners flood teams with noise

273 posts from 273 people on Glyph Ibis, GitHub issues, Reddit.

NVIDIA vulnerabilities are hard to triage and patch

77 posts from 77 people on Glyph Ibis.

AWS vulnerabilities are hard to triage and patch

65 posts from 65 people on Glyph Ibis.

IBM vulnerabilities are hard to triage and patch

35 posts from 35 people on Glyph Ibis.

GitHub vulnerabilities are hard to triage and patch

12 posts from 11 people on GitHub issues, Glyph Ibis, Hacker News.

JetBrains vulnerabilities are hard to triage and patch

12 posts from 12 people on Glyph Ibis.

vLLM vulnerabilities are hard to triage and patch

9 posts from 9 people on Glyph Ibis.

Red Hat vulnerabilities are hard to triage and patch

8 posts from 8 people on Glyph Ibis.

Model Context Protocol vulnerabilities are hard to triage and patch

6 posts from 6 people on Glyph Ibis, GitHub issues.

Claude Code vulnerabilities are hard to triage and patch

5 posts from 5 people on GitHub issues.

Other PyTorch problems

PyTorch GPU access and drivers are painful

14 posts from 14 people on GitHub issues.

PyTorch upgrades break working setups

26 posts from 21 people on GitHub issues, Reddit.

PyTorch users keep filing bugs

Top post: "Meta-issue: torch.compile gaps found via the CPython test suite", one of 46 posts from 37 people on GitHub issues, Reddit.

Trouble with PyTorch values

Top post: "How can I sum elements of a tensor based on a condition of one out of two values in its index pair into a new", one of 3 posts from 3 people on GitHub issues, Stack Overflow.

Trouble with PyTorch causing

Top post: "PyVista plotting running slowly, resetting box size and causing collisions", one of 3 posts from 3 people on GitHub issues, Stack Overflow.

PyTorch deprecations force unplanned migrations

8 posts from 5 people on GitHub issues.

Trouble with PyTorch true

Top post: "PaddleOCR-VL: position embedding interpolation changed from align_corners=False to True", one of 9 posts from 6 people on GitHub issues.

Trouble with PyTorch inductor

Top post: "`[Inductor][CPU] torch.var returns NaN for large-magnitude constant float64 inputs while eager returns 0`", one of 12 posts from 9 people on GitHub issues.

PyTorch builds are slow or flaky

9 posts from 1 person on GitHub issues. Unverified.

Trouble with PyTorch input

Top post: "Generation crashes with encoder_repetition_penalty when encoder_outputs are provided without input_ids", one of 6 posts from 6 people on GitHub issues.

Running PyTorch locally hits memory and speed limits

5 posts from 5 people on GitHub issues, Hacker News.

PyTorch lock-in makes switching costly

4 posts from 4 people on GitHub issues.

History

First seen with 3 posts.

Sep 25, 2026