# DataHub v1.7.0.1 bounds lineage traversal and tightens lineage API access

NEWS, 3 SEP 2026, read 10 Nov 2026

**The short answer.** DataHub v1.7.0.1, released on 3 Sep 2026, bounds scrollAcrossLineage so wide lineage graphs no longer risk exhausting GMS memory. The patch also redacts unauthorized OpenAPI lineage scroll results as restricted, removes a hardcoded default system client secret, and bumps dependencies for known CVEs.

DataHub published patch release v1.7.0.1 on 3 Sep 2026. The notes list lineage correctness fixes alongside authorization tightening and dependency updates for known vulnerabilities.

On lineage specifically, scrollAcrossLineage is now bounded to prevent GMS out-of-memory failures on wide graphs. Unauthorized OpenAPI lineage scroll endpoints are redacted as restricted, so lineage reads follow entity permissions.

The release also removes the hardcoded systemClientSecret default. Deployments that relied on the built-in value must set DATAHUB_SYSTEM_CLIENT_SECRET on GMS, the MAE and MCE consumers, the frontend and Actions before upgrading. A pre-1.7.0 deployment must move through v1.6.0 first.

## More lineage news

- [OpenLineage 1.55.0 adds dbt Core v2 support with live events](/news/openlineage-1-55-dbt-core-v2-live-events/): 30 Oct 2026
- [dbt MCP server v2.10.0 documents get_column_lineage arguments](/news/dbt-mcp-2-10-0-column-lineage-tool/): 30 Oct 2026
- [Alation ships version 1.0.0 of its AI agent SDK and MCP server](/news/alation-ai-agent-sdk-1-0-0/): 26 Oct 2026
- [DataHub v1.8.0 adds metrics as lineage upstreams, off by default](/news/datahub-1-8-0-metrics-column-lineage/): 22 Oct 2026

## Sources

- github.com/datahub-project/datahub/releases/tag/v1.7.0.1: https://github.com/datahub-project/datahub/releases/tag/v1.7.0.1 (read 10 Nov 2026)

Last reviewed 10 Nov 2026. Canonical: https://datalineagecompare.com/news/datahub-1-7-0-1-lineage-fixes/
