Repository navigation
chore(specs): security scan findings - #593
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #593 +/- ##
=======================================
Coverage 83.35% 83.36%
=======================================
Files 1235 1235
Lines 126548 126550 +2
=======================================
+ Hits 105483 105497 +14
+ Misses 21056 21044 -12
Partials 9 9
🚀 New features to boost your workflow:
|
compileSchema now installs a URL loader that refuses every load, so an agent-reported schema can no longer make the API node open file:// paths (security scan 2026-10-18, finding I1). Draft metaschemas and in-document refs keep working. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
pg_isready over the unix socket succeeds against the docker entrypoint's temporary init server, which then restarts, so the final check raced it. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
fclairamb
added a commit
that referenced
this pull request
Oct 19, 2026
Specs for the open findings of the daily security scan. Specs only, no code change. ## Specs | Spec | Severity | Finding | Summary | |---|---|---|---| | `specs/todos/2026-10-19-01-a2a-response-size-cap.md` | medium | J1 (2026-10-19) | The A2A client (Agent Card fetch, `SendMessage`, `GetTask`, through the a2a-go SDK) reads success response bodies with no size cap. Only the 30 s timeout bounds them. A member pointing an A2A integration at their own server can exhaust the server's memory. Fix: a capped reader in `a2aStatusTransport`. | Scan of 2026-10-19 covered: - the new A2A notification channel (#596), which held on egress, tenancy, secrets and comment rendering apart from J1; - the docs redesign; - the dash0 changes. It also verified the plugin-schema `$ref` fix of #593 (I1). No other new finding. 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Specs for the open findings of the daily security scan. Specs only, no code change.
Specs
specs/todos/2026-10-18-01-plugin-schema-file-ref.mdfile://references. An agent-reported schema can therefore make the API node open local files, and whether the type gets listed reveals whether a path or JSON key exists. Fix:compiler.UseLoaderwith a loader that refuses every URL.Autopilot implemented the spec (
fix(plugins): refuse external $ref targets in plugin schemas) and archived it inspecs/done/2026/10/. Batch gate green:make build-backend lint-back test(258 packages ok).Decided by autopilot
None: the spec had no open questions.
Scan of 2026-10-18: the new plugin system, public tools endpoint, vendor-status check, SMS/voice quotas and MCP handshake change were reviewed. The postgres fix of #584 (G1/G2) was verified. No other new finding.
🤖 Generated with Claude Code