Cairn
NousResearch/hermes-agent

Unbounded HTTP response body reads need caps

Cluster 54780 · hermes cli. Data as of

2 open items. Fix attempted, not merged.

The short answer

1open issue
1open PR
3items grouped
Known?
Yes. 3 related items grouped here, 1 issue already closed.
Fix event
No fix has been merged to main. see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 1 PR.

These issues and PRs concern HTTP response bodies being read without size limits in CLI enrollment and billing client code. Fixes involve bounding those reads to prevent uncapped memory consumption.

Open issues1

  • Issue#54780Nous billing client reads response bodies without a cap

Open PRs1

  • PR#54781fix(nous): bound billing response reads
Closed issues · 1
  • Closed#54953Nous billing client reads portal JSON responses without a body cap
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.45: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means every pair is linked.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Subsystem
hermes cli
Closed issues
1
Attempts
0 PRs closed without merging

For your agent

The same facts, typed.

cluster/54780.json
cluster/54780.md