Matti Nannt b7f155185f fix(security): strip sensitive survey and segment metadata from public client API ...

Segment filter conditions, titles, descriptions, and survey names were
all included in the GET /api/v1/client/{environmentId}/environment response,
which is publicly readable by anyone with the environment ID. A security
researcher reported that filter values can contain enterprise customer names
and other confidential targeting data (ENG-858).

None of these fields are functionally required by the SDK:
- Segment matching is evaluated server-side; the SDK only needs segment IDs
- filter.length > 0 is replaced with a hasFilters boolean
- survey.name was only used in debug log statements; replaced with survey.id
- segment.title and segment.description were completely unused in all SDK packages

The public segment shape is now { id, hasFilters } — no targeting logic leaves
the backend.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

2026-05-05 08:47:58 +02:00

..

storybook

chore(deps): bump the npm_and_yarn group across 5 directories with 2 updates (#7834)

2026-04-28 12:01:12 +02:00

web

fix(security): strip sensitive survey and segment metadata from public client API

2026-05-05 08:47:58 +02:00