Security context

What an agent needs to avoid regressing past fixes and find the next vuln in this repo.

specklesystems/speckle-sharp
main @ e4bb61d
2
Fixes
0
CVEs
MEDIUM
Peak severity
50.0%
Coverage
Highlights
Auth Bypass: 1 prior fix. Scrutinize any change in this area.
Core/Core/Logging/SpeckleLog.cs: most-fixed (1 issue). Treat as high-risk during review.
0 high-severity fixes in this history; regressions here are high-impact.
Recurring patterns

The bug types that recur here, drawn from past fixes, not open vulnerabilities.

Auth Bypass: Inadequate verification of client-side stream ownership or contributor roles can allow unauthorized users to fetch or interact with restricted streams. Developers must enforce role permission checks prior to invoking stream retrieval APIs.
Information Disclosure: Logging configurations that automatically enrich logs with client IPs and user-agent data create risk of accidental PII leakage. Removing automatic IP-tracking telemetry libraries and using explicit opt-in logging safeguards user privacy.