Cairn
NousResearch/hermes-agent

Cap unbounded response body reads in Nous account lookup

Cluster 54777 · hermes cli. Data as of

2 open items. Fix attempted, not merged.

The short answer

1open issue
1open PR
4items grouped
Known?
Yes. 4 related items grouped here, 1 issue already closed.
Fix event
No fix has been merged to main. 1 PR closed without merging; 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 address a vulnerability where Nous Portal account lookup and refresh requests read HTTP response bodies without any size limit. The fixes introduce a cap on response body reads to prevent unbounded memory consumption.

Open issues1

  • Issue#54777Nous account lookup reads Portal response bodies without a cap

Open PRs1

  • PR#54778fix(nous): bound account response reads

1 PR closed without merging

From the close comments: superseded by another PR 1

  • #56509 fix(nous): cap response body size in account info fetch · superseded by another PR → #54778
Closed issues · 1
  • Closed#56507Nous Portal account refresh reads response bodies without a cap
How this cluster was grouped
  • Link evidence (structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
  • Pairwise link density 0.56: 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
1 PR closed without merging

For your agent

The same facts, typed.

cluster/54777.json
cluster/54777.md