langgraph-sdk
Build resilient agents.
View on Github
Activity
- Latest release
- 2w ago
- Total releases
- 102
- Cadence
- ~5 days
- Last 12 months
- 25
Reach
- Stars
- 40.9k
Details
- License
- MIT
- First release
- May 02, 2024
| Version | Released | |
|---|---|---|
0.4.4
patch
| ||
0.4.3
patch
| ||
0.4.2
patch
| ||
0.4.1
patch
| ||
0.4.0
minor
| ||
0.3.15
patch
| ||
0.3.14
patch
1 CVE
CVE-2026-48776
PYSEC-2026-2575
GHSA-w39p-vh2g-g8g5
PYSEC-2026-2194
Jul 13, 2026
LangGraph SDK has unsafe URL path construction
4.2
/ 10
Medium
Network
High
Low
None
Unchanged
Low
Low
None
Summary
This issue is most consequential in deployments that:
There have no evidence of this behavior being triggered in the wild. This change is intended to reduce the surface available when caller-supplied identifier values originate from untrusted sources. Affected users / systemsYou may be affected if you:
Applications that validate identifier values (for example, by parsing them as UUIDs and rejecting anything that does not parse) before passing them to SDK methods are not affected. Validated UUIDs round-trip through the SDK request path unchanged. Impact
Patches / mitigationThe SDK now applies path-segment encoding to identifier values before they are interpolated into request URL templates. After this change, identifier values that contain characters with special meaning in URL paths are transmitted as encoded byte sequences and routed to the resource the SDK method's call site indicates. CompatibilityIdentifier values that match the standard UUID format, or any other format that contains only characters safe to transmit unencoded in URL path segments, round-trip through the SDK request path unchanged. Applications that already validate identifier inputs see no behavioral change. Operational guidance
LangSmith / hosted deployments noteThis issue affects the SDK that runs in caller applications. The LangGraph server runtime, including LangSmith-hosted deployments, receives ordinary HTTP requests on documented routes and is not itself affected by this issue. Applications that consume LangSmith-hosted services via First reported by: pucagit (CyStack). Affected versions
0.1.0
0.1.1
0.1.10
0.1.11
0.1.12
0.1.14
0.1.16
0.1.17
0.1.18
0.1.2
0.1.20
0.1.21
+ 84 more Show less
0.1.22
0.1.23
0.1.24
0.1.25
0.1.26
0.1.27
0.1.28
0.1.29
0.1.3
0.1.30
0.1.31
0.1.32
0.1.33
0.1.34
0.1.35
0.1.36
0.1.37
0.1.38
0.1.39
0.1.4
0.1.40
0.1.42
0.1.43
0.1.44
0.1.45
0.1.46
0.1.47
0.1.48
0.1.5
0.1.50
0.1.51
0.1.53
0.1.55
0.1.56
0.1.57
0.1.58
0.1.59
0.1.6
0.1.60
0.1.61
0.1.62
0.1.63
0.1.64
0.1.65
0.1.66
0.1.69
0.1.7
0.1.70
0.1.71
0.1.72
0.1.73
0.1.74
0.1.8
0.1.9
0.2.0
0.2.0a1
0.2.1
0.2.10
0.2.12
0.2.14
0.2.15
0.2.2
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.10
0.3.11
0.3.12
0.3.13
0.3.14
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.3.8
0.3.9
Fixed in
0.3.15
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.3.13
patch
1 CVE
CVE-2026-48776
PYSEC-2026-2575
GHSA-w39p-vh2g-g8g5
PYSEC-2026-2194
Jul 13, 2026
LangGraph SDK has unsafe URL path construction
4.2
/ 10
Medium
Network
High
Low
None
Unchanged
Low
Low
None
Summary
This issue is most consequential in deployments that:
There have no evidence of this behavior being triggered in the wild. This change is intended to reduce the surface available when caller-supplied identifier values originate from untrusted sources. Affected users / systemsYou may be affected if you:
Applications that validate identifier values (for example, by parsing them as UUIDs and rejecting anything that does not parse) before passing them to SDK methods are not affected. Validated UUIDs round-trip through the SDK request path unchanged. Impact
Patches / mitigationThe SDK now applies path-segment encoding to identifier values before they are interpolated into request URL templates. After this change, identifier values that contain characters with special meaning in URL paths are transmitted as encoded byte sequences and routed to the resource the SDK method's call site indicates. CompatibilityIdentifier values that match the standard UUID format, or any other format that contains only characters safe to transmit unencoded in URL path segments, round-trip through the SDK request path unchanged. Applications that already validate identifier inputs see no behavioral change. Operational guidance
LangSmith / hosted deployments noteThis issue affects the SDK that runs in caller applications. The LangGraph server runtime, including LangSmith-hosted deployments, receives ordinary HTTP requests on documented routes and is not itself affected by this issue. Applications that consume LangSmith-hosted services via First reported by: pucagit (CyStack). Affected versions
0.1.0
0.1.1
0.1.10
0.1.11
0.1.12
0.1.14
0.1.16
0.1.17
0.1.18
0.1.2
0.1.20
0.1.21
+ 84 more Show less
0.1.22
0.1.23
0.1.24
0.1.25
0.1.26
0.1.27
0.1.28
0.1.29
0.1.3
0.1.30
0.1.31
0.1.32
0.1.33
0.1.34
0.1.35
0.1.36
0.1.37
0.1.38
0.1.39
0.1.4
0.1.40
0.1.42
0.1.43
0.1.44
0.1.45
0.1.46
0.1.47
0.1.48
0.1.5
0.1.50
0.1.51
0.1.53
0.1.55
0.1.56
0.1.57
0.1.58
0.1.59
0.1.6
0.1.60
0.1.61
0.1.62
0.1.63
0.1.64
0.1.65
0.1.66
0.1.69
0.1.7
0.1.70
0.1.71
0.1.72
0.1.73
0.1.74
0.1.8
0.1.9
0.2.0
0.2.0a1
0.2.1
0.2.10
0.2.12
0.2.14
0.2.15
0.2.2
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.10
0.3.11
0.3.12
0.3.13
0.3.14
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.3.8
0.3.9
Fixed in
0.3.15
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.3.12
patch
1 CVE
CVE-2026-48776
PYSEC-2026-2575
GHSA-w39p-vh2g-g8g5
PYSEC-2026-2194
Jul 13, 2026
LangGraph SDK has unsafe URL path construction
4.2
/ 10
Medium
Network
High
Low
None
Unchanged
Low
Low
None
Summary
This issue is most consequential in deployments that:
There have no evidence of this behavior being triggered in the wild. This change is intended to reduce the surface available when caller-supplied identifier values originate from untrusted sources. Affected users / systemsYou may be affected if you:
Applications that validate identifier values (for example, by parsing them as UUIDs and rejecting anything that does not parse) before passing them to SDK methods are not affected. Validated UUIDs round-trip through the SDK request path unchanged. Impact
Patches / mitigationThe SDK now applies path-segment encoding to identifier values before they are interpolated into request URL templates. After this change, identifier values that contain characters with special meaning in URL paths are transmitted as encoded byte sequences and routed to the resource the SDK method's call site indicates. CompatibilityIdentifier values that match the standard UUID format, or any other format that contains only characters safe to transmit unencoded in URL path segments, round-trip through the SDK request path unchanged. Applications that already validate identifier inputs see no behavioral change. Operational guidance
LangSmith / hosted deployments noteThis issue affects the SDK that runs in caller applications. The LangGraph server runtime, including LangSmith-hosted deployments, receives ordinary HTTP requests on documented routes and is not itself affected by this issue. Applications that consume LangSmith-hosted services via First reported by: pucagit (CyStack). Affected versions
0.1.0
0.1.1
0.1.10
0.1.11
0.1.12
0.1.14
0.1.16
0.1.17
0.1.18
0.1.2
0.1.20
0.1.21
+ 84 more Show less
0.1.22
0.1.23
0.1.24
0.1.25
0.1.26
0.1.27
0.1.28
0.1.29
0.1.3
0.1.30
0.1.31
0.1.32
0.1.33
0.1.34
0.1.35
0.1.36
0.1.37
0.1.38
0.1.39
0.1.4
0.1.40
0.1.42
0.1.43
0.1.44
0.1.45
0.1.46
0.1.47
0.1.48
0.1.5
0.1.50
0.1.51
0.1.53
0.1.55
0.1.56
0.1.57
0.1.58
0.1.59
0.1.6
0.1.60
0.1.61
0.1.62
0.1.63
0.1.64
0.1.65
0.1.66
0.1.69
0.1.7
0.1.70
0.1.71
0.1.72
0.1.73
0.1.74
0.1.8
0.1.9
0.2.0
0.2.0a1
0.2.1
0.2.10
0.2.12
0.2.14
0.2.15
0.2.2
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.10
0.3.11
0.3.12
0.3.13
0.3.14
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.3.8
0.3.9
Fixed in
0.3.15
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.3.11
patch
1 CVE
CVE-2026-48776
PYSEC-2026-2575
GHSA-w39p-vh2g-g8g5
PYSEC-2026-2194
Jul 13, 2026
LangGraph SDK has unsafe URL path construction
4.2
/ 10
Medium
Network
High
Low
None
Unchanged
Low
Low
None
Summary
This issue is most consequential in deployments that:
There have no evidence of this behavior being triggered in the wild. This change is intended to reduce the surface available when caller-supplied identifier values originate from untrusted sources. Affected users / systemsYou may be affected if you:
Applications that validate identifier values (for example, by parsing them as UUIDs and rejecting anything that does not parse) before passing them to SDK methods are not affected. Validated UUIDs round-trip through the SDK request path unchanged. Impact
Patches / mitigationThe SDK now applies path-segment encoding to identifier values before they are interpolated into request URL templates. After this change, identifier values that contain characters with special meaning in URL paths are transmitted as encoded byte sequences and routed to the resource the SDK method's call site indicates. CompatibilityIdentifier values that match the standard UUID format, or any other format that contains only characters safe to transmit unencoded in URL path segments, round-trip through the SDK request path unchanged. Applications that already validate identifier inputs see no behavioral change. Operational guidance
LangSmith / hosted deployments noteThis issue affects the SDK that runs in caller applications. The LangGraph server runtime, including LangSmith-hosted deployments, receives ordinary HTTP requests on documented routes and is not itself affected by this issue. Applications that consume LangSmith-hosted services via First reported by: pucagit (CyStack). Affected versions
0.1.0
0.1.1
0.1.10
0.1.11
0.1.12
0.1.14
0.1.16
0.1.17
0.1.18
0.1.2
0.1.20
0.1.21
+ 84 more Show less
0.1.22
0.1.23
0.1.24
0.1.25
0.1.26
0.1.27
0.1.28
0.1.29
0.1.3
0.1.30
0.1.31
0.1.32
0.1.33
0.1.34
0.1.35
0.1.36
0.1.37
0.1.38
0.1.39
0.1.4
0.1.40
0.1.42
0.1.43
0.1.44
0.1.45
0.1.46
0.1.47
0.1.48
0.1.5
0.1.50
0.1.51
0.1.53
0.1.55
0.1.56
0.1.57
0.1.58
0.1.59
0.1.6
0.1.60
0.1.61
0.1.62
0.1.63
0.1.64
0.1.65
0.1.66
0.1.69
0.1.7
0.1.70
0.1.71
0.1.72
0.1.73
0.1.74
0.1.8
0.1.9
0.2.0
0.2.0a1
0.2.1
0.2.10
0.2.12
0.2.14
0.2.15
0.2.2
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.10
0.3.11
0.3.12
0.3.13
0.3.14
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.3.8
0.3.9
Fixed in
0.3.15
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.3.10
patch
1 CVE
CVE-2026-48776
PYSEC-2026-2575
GHSA-w39p-vh2g-g8g5
PYSEC-2026-2194
Jul 13, 2026
LangGraph SDK has unsafe URL path construction
4.2
/ 10
Medium
Network
High
Low
None
Unchanged
Low
Low
None
Summary
This issue is most consequential in deployments that:
There have no evidence of this behavior being triggered in the wild. This change is intended to reduce the surface available when caller-supplied identifier values originate from untrusted sources. Affected users / systemsYou may be affected if you:
Applications that validate identifier values (for example, by parsing them as UUIDs and rejecting anything that does not parse) before passing them to SDK methods are not affected. Validated UUIDs round-trip through the SDK request path unchanged. Impact
Patches / mitigationThe SDK now applies path-segment encoding to identifier values before they are interpolated into request URL templates. After this change, identifier values that contain characters with special meaning in URL paths are transmitted as encoded byte sequences and routed to the resource the SDK method's call site indicates. CompatibilityIdentifier values that match the standard UUID format, or any other format that contains only characters safe to transmit unencoded in URL path segments, round-trip through the SDK request path unchanged. Applications that already validate identifier inputs see no behavioral change. Operational guidance
LangSmith / hosted deployments noteThis issue affects the SDK that runs in caller applications. The LangGraph server runtime, including LangSmith-hosted deployments, receives ordinary HTTP requests on documented routes and is not itself affected by this issue. Applications that consume LangSmith-hosted services via First reported by: pucagit (CyStack). Affected versions
0.1.0
0.1.1
0.1.10
0.1.11
0.1.12
0.1.14
0.1.16
0.1.17
0.1.18
0.1.2
0.1.20
0.1.21
+ 84 more Show less
0.1.22
0.1.23
0.1.24
0.1.25
0.1.26
0.1.27
0.1.28
0.1.29
0.1.3
0.1.30
0.1.31
0.1.32
0.1.33
0.1.34
0.1.35
0.1.36
0.1.37
0.1.38
0.1.39
0.1.4
0.1.40
0.1.42
0.1.43
0.1.44
0.1.45
0.1.46
0.1.47
0.1.48
0.1.5
0.1.50
0.1.51
0.1.53
0.1.55
0.1.56
0.1.57
0.1.58
0.1.59
0.1.6
0.1.60
0.1.61
0.1.62
0.1.63
0.1.64
0.1.65
0.1.66
0.1.69
0.1.7
0.1.70
0.1.71
0.1.72
0.1.73
0.1.74
0.1.8
0.1.9
0.2.0
0.2.0a1
0.2.1
0.2.10
0.2.12
0.2.14
0.2.15
0.2.2
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.10
0.3.11
0.3.12
0.3.13
0.3.14
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.3.8
0.3.9
Fixed in
0.3.15
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.3.9
patch
1 CVE
CVE-2026-48776
PYSEC-2026-2575
GHSA-w39p-vh2g-g8g5
PYSEC-2026-2194
Jul 13, 2026
LangGraph SDK has unsafe URL path construction
4.2
/ 10
Medium
Network
High
Low
None
Unchanged
Low
Low
None
Summary
This issue is most consequential in deployments that:
There have no evidence of this behavior being triggered in the wild. This change is intended to reduce the surface available when caller-supplied identifier values originate from untrusted sources. Affected users / systemsYou may be affected if you:
Applications that validate identifier values (for example, by parsing them as UUIDs and rejecting anything that does not parse) before passing them to SDK methods are not affected. Validated UUIDs round-trip through the SDK request path unchanged. Impact
Patches / mitigationThe SDK now applies path-segment encoding to identifier values before they are interpolated into request URL templates. After this change, identifier values that contain characters with special meaning in URL paths are transmitted as encoded byte sequences and routed to the resource the SDK method's call site indicates. CompatibilityIdentifier values that match the standard UUID format, or any other format that contains only characters safe to transmit unencoded in URL path segments, round-trip through the SDK request path unchanged. Applications that already validate identifier inputs see no behavioral change. Operational guidance
LangSmith / hosted deployments noteThis issue affects the SDK that runs in caller applications. The LangGraph server runtime, including LangSmith-hosted deployments, receives ordinary HTTP requests on documented routes and is not itself affected by this issue. Applications that consume LangSmith-hosted services via First reported by: pucagit (CyStack). Affected versions
0.1.0
0.1.1
0.1.10
0.1.11
0.1.12
0.1.14
0.1.16
0.1.17
0.1.18
0.1.2
0.1.20
0.1.21
+ 84 more Show less
0.1.22
0.1.23
0.1.24
0.1.25
0.1.26
0.1.27
0.1.28
0.1.29
0.1.3
0.1.30
0.1.31
0.1.32
0.1.33
0.1.34
0.1.35
0.1.36
0.1.37
0.1.38
0.1.39
0.1.4
0.1.40
0.1.42
0.1.43
0.1.44
0.1.45
0.1.46
0.1.47
0.1.48
0.1.5
0.1.50
0.1.51
0.1.53
0.1.55
0.1.56
0.1.57
0.1.58
0.1.59
0.1.6
0.1.60
0.1.61
0.1.62
0.1.63
0.1.64
0.1.65
0.1.66
0.1.69
0.1.7
0.1.70
0.1.71
0.1.72
0.1.73
0.1.74
0.1.8
0.1.9
0.2.0
0.2.0a1
0.2.1
0.2.10
0.2.12
0.2.14
0.2.15
0.2.2
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.10
0.3.11
0.3.12
0.3.13
0.3.14
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.3.8
0.3.9
Fixed in
0.3.15
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.3.8
patch
1 CVE
CVE-2026-48776
PYSEC-2026-2575
GHSA-w39p-vh2g-g8g5
PYSEC-2026-2194
Jul 13, 2026
LangGraph SDK has unsafe URL path construction
4.2
/ 10
Medium
Network
High
Low
None
Unchanged
Low
Low
None
Summary
This issue is most consequential in deployments that:
There have no evidence of this behavior being triggered in the wild. This change is intended to reduce the surface available when caller-supplied identifier values originate from untrusted sources. Affected users / systemsYou may be affected if you:
Applications that validate identifier values (for example, by parsing them as UUIDs and rejecting anything that does not parse) before passing them to SDK methods are not affected. Validated UUIDs round-trip through the SDK request path unchanged. Impact
Patches / mitigationThe SDK now applies path-segment encoding to identifier values before they are interpolated into request URL templates. After this change, identifier values that contain characters with special meaning in URL paths are transmitted as encoded byte sequences and routed to the resource the SDK method's call site indicates. CompatibilityIdentifier values that match the standard UUID format, or any other format that contains only characters safe to transmit unencoded in URL path segments, round-trip through the SDK request path unchanged. Applications that already validate identifier inputs see no behavioral change. Operational guidance
LangSmith / hosted deployments noteThis issue affects the SDK that runs in caller applications. The LangGraph server runtime, including LangSmith-hosted deployments, receives ordinary HTTP requests on documented routes and is not itself affected by this issue. Applications that consume LangSmith-hosted services via First reported by: pucagit (CyStack). Affected versions
0.1.0
0.1.1
0.1.10
0.1.11
0.1.12
0.1.14
0.1.16
0.1.17
0.1.18
0.1.2
0.1.20
0.1.21
+ 84 more Show less
0.1.22
0.1.23
0.1.24
0.1.25
0.1.26
0.1.27
0.1.28
0.1.29
0.1.3
0.1.30
0.1.31
0.1.32
0.1.33
0.1.34
0.1.35
0.1.36
0.1.37
0.1.38
0.1.39
0.1.4
0.1.40
0.1.42
0.1.43
0.1.44
0.1.45
0.1.46
0.1.47
0.1.48
0.1.5
0.1.50
0.1.51
0.1.53
0.1.55
0.1.56
0.1.57
0.1.58
0.1.59
0.1.6
0.1.60
0.1.61
0.1.62
0.1.63
0.1.64
0.1.65
0.1.66
0.1.69
0.1.7
0.1.70
0.1.71
0.1.72
0.1.73
0.1.74
0.1.8
0.1.9
0.2.0
0.2.0a1
0.2.1
0.2.10
0.2.12
0.2.14
0.2.15
0.2.2
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.10
0.3.11
0.3.12
0.3.13
0.3.14
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.3.8
0.3.9
Fixed in
0.3.15
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.3.7
patch
1 CVE
CVE-2026-48776
PYSEC-2026-2575
GHSA-w39p-vh2g-g8g5
PYSEC-2026-2194
Jul 13, 2026
LangGraph SDK has unsafe URL path construction
4.2
/ 10
Medium
Network
High
Low
None
Unchanged
Low
Low
None
Summary
This issue is most consequential in deployments that:
There have no evidence of this behavior being triggered in the wild. This change is intended to reduce the surface available when caller-supplied identifier values originate from untrusted sources. Affected users / systemsYou may be affected if you:
Applications that validate identifier values (for example, by parsing them as UUIDs and rejecting anything that does not parse) before passing them to SDK methods are not affected. Validated UUIDs round-trip through the SDK request path unchanged. Impact
Patches / mitigationThe SDK now applies path-segment encoding to identifier values before they are interpolated into request URL templates. After this change, identifier values that contain characters with special meaning in URL paths are transmitted as encoded byte sequences and routed to the resource the SDK method's call site indicates. CompatibilityIdentifier values that match the standard UUID format, or any other format that contains only characters safe to transmit unencoded in URL path segments, round-trip through the SDK request path unchanged. Applications that already validate identifier inputs see no behavioral change. Operational guidance
LangSmith / hosted deployments noteThis issue affects the SDK that runs in caller applications. The LangGraph server runtime, including LangSmith-hosted deployments, receives ordinary HTTP requests on documented routes and is not itself affected by this issue. Applications that consume LangSmith-hosted services via First reported by: pucagit (CyStack). Affected versions
0.1.0
0.1.1
0.1.10
0.1.11
0.1.12
0.1.14
0.1.16
0.1.17
0.1.18
0.1.2
0.1.20
0.1.21
+ 84 more Show less
0.1.22
0.1.23
0.1.24
0.1.25
0.1.26
0.1.27
0.1.28
0.1.29
0.1.3
0.1.30
0.1.31
0.1.32
0.1.33
0.1.34
0.1.35
0.1.36
0.1.37
0.1.38
0.1.39
0.1.4
0.1.40
0.1.42
0.1.43
0.1.44
0.1.45
0.1.46
0.1.47
0.1.48
0.1.5
0.1.50
0.1.51
0.1.53
0.1.55
0.1.56
0.1.57
0.1.58
0.1.59
0.1.6
0.1.60
0.1.61
0.1.62
0.1.63
0.1.64
0.1.65
0.1.66
0.1.69
0.1.7
0.1.70
0.1.71
0.1.72
0.1.73
0.1.74
0.1.8
0.1.9
0.2.0
0.2.0a1
0.2.1
0.2.10
0.2.12
0.2.14
0.2.15
0.2.2
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.10
0.3.11
0.3.12
0.3.13
0.3.14
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.3.8
0.3.9
Fixed in
0.3.15
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.3.6
patch
1 CVE
CVE-2026-48776
PYSEC-2026-2575
GHSA-w39p-vh2g-g8g5
PYSEC-2026-2194
Jul 13, 2026
LangGraph SDK has unsafe URL path construction
4.2
/ 10
Medium
Network
High
Low
None
Unchanged
Low
Low
None
Summary
This issue is most consequential in deployments that:
There have no evidence of this behavior being triggered in the wild. This change is intended to reduce the surface available when caller-supplied identifier values originate from untrusted sources. Affected users / systemsYou may be affected if you:
Applications that validate identifier values (for example, by parsing them as UUIDs and rejecting anything that does not parse) before passing them to SDK methods are not affected. Validated UUIDs round-trip through the SDK request path unchanged. Impact
Patches / mitigationThe SDK now applies path-segment encoding to identifier values before they are interpolated into request URL templates. After this change, identifier values that contain characters with special meaning in URL paths are transmitted as encoded byte sequences and routed to the resource the SDK method's call site indicates. CompatibilityIdentifier values that match the standard UUID format, or any other format that contains only characters safe to transmit unencoded in URL path segments, round-trip through the SDK request path unchanged. Applications that already validate identifier inputs see no behavioral change. Operational guidance
LangSmith / hosted deployments noteThis issue affects the SDK that runs in caller applications. The LangGraph server runtime, including LangSmith-hosted deployments, receives ordinary HTTP requests on documented routes and is not itself affected by this issue. Applications that consume LangSmith-hosted services via First reported by: pucagit (CyStack). Affected versions
0.1.0
0.1.1
0.1.10
0.1.11
0.1.12
0.1.14
0.1.16
0.1.17
0.1.18
0.1.2
0.1.20
0.1.21
+ 84 more Show less
0.1.22
0.1.23
0.1.24
0.1.25
0.1.26
0.1.27
0.1.28
0.1.29
0.1.3
0.1.30
0.1.31
0.1.32
0.1.33
0.1.34
0.1.35
0.1.36
0.1.37
0.1.38
0.1.39
0.1.4
0.1.40
0.1.42
0.1.43
0.1.44
0.1.45
0.1.46
0.1.47
0.1.48
0.1.5
0.1.50
0.1.51
0.1.53
0.1.55
0.1.56
0.1.57
0.1.58
0.1.59
0.1.6
0.1.60
0.1.61
0.1.62
0.1.63
0.1.64
0.1.65
0.1.66
0.1.69
0.1.7
0.1.70
0.1.71
0.1.72
0.1.73
0.1.74
0.1.8
0.1.9
0.2.0
0.2.0a1
0.2.1
0.2.10
0.2.12
0.2.14
0.2.15
0.2.2
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.10
0.3.11
0.3.12
0.3.13
0.3.14
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.3.8
0.3.9
Fixed in
0.3.15
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.3.5
patch
1 CVE
CVE-2026-48776
PYSEC-2026-2575
GHSA-w39p-vh2g-g8g5
PYSEC-2026-2194
Jul 13, 2026
LangGraph SDK has unsafe URL path construction
4.2
/ 10
Medium
Network
High
Low
None
Unchanged
Low
Low
None
Summary
This issue is most consequential in deployments that:
There have no evidence of this behavior being triggered in the wild. This change is intended to reduce the surface available when caller-supplied identifier values originate from untrusted sources. Affected users / systemsYou may be affected if you:
Applications that validate identifier values (for example, by parsing them as UUIDs and rejecting anything that does not parse) before passing them to SDK methods are not affected. Validated UUIDs round-trip through the SDK request path unchanged. Impact
Patches / mitigationThe SDK now applies path-segment encoding to identifier values before they are interpolated into request URL templates. After this change, identifier values that contain characters with special meaning in URL paths are transmitted as encoded byte sequences and routed to the resource the SDK method's call site indicates. CompatibilityIdentifier values that match the standard UUID format, or any other format that contains only characters safe to transmit unencoded in URL path segments, round-trip through the SDK request path unchanged. Applications that already validate identifier inputs see no behavioral change. Operational guidance
LangSmith / hosted deployments noteThis issue affects the SDK that runs in caller applications. The LangGraph server runtime, including LangSmith-hosted deployments, receives ordinary HTTP requests on documented routes and is not itself affected by this issue. Applications that consume LangSmith-hosted services via First reported by: pucagit (CyStack). Affected versions
0.1.0
0.1.1
0.1.10
0.1.11
0.1.12
0.1.14
0.1.16
0.1.17
0.1.18
0.1.2
0.1.20
0.1.21
+ 84 more Show less
0.1.22
0.1.23
0.1.24
0.1.25
0.1.26
0.1.27
0.1.28
0.1.29
0.1.3
0.1.30
0.1.31
0.1.32
0.1.33
0.1.34
0.1.35
0.1.36
0.1.37
0.1.38
0.1.39
0.1.4
0.1.40
0.1.42
0.1.43
0.1.44
0.1.45
0.1.46
0.1.47
0.1.48
0.1.5
0.1.50
0.1.51
0.1.53
0.1.55
0.1.56
0.1.57
0.1.58
0.1.59
0.1.6
0.1.60
0.1.61
0.1.62
0.1.63
0.1.64
0.1.65
0.1.66
0.1.69
0.1.7
0.1.70
0.1.71
0.1.72
0.1.73
0.1.74
0.1.8
0.1.9
0.2.0
0.2.0a1
0.2.1
0.2.10
0.2.12
0.2.14
0.2.15
0.2.2
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.10
0.3.11
0.3.12
0.3.13
0.3.14
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.3.8
0.3.9
Fixed in
0.3.15
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.3.4
patch
1 CVE
CVE-2026-48776
PYSEC-2026-2575
GHSA-w39p-vh2g-g8g5
PYSEC-2026-2194
Jul 13, 2026
LangGraph SDK has unsafe URL path construction
4.2
/ 10
Medium
Network
High
Low
None
Unchanged
Low
Low
None
Summary
This issue is most consequential in deployments that:
There have no evidence of this behavior being triggered in the wild. This change is intended to reduce the surface available when caller-supplied identifier values originate from untrusted sources. Affected users / systemsYou may be affected if you:
Applications that validate identifier values (for example, by parsing them as UUIDs and rejecting anything that does not parse) before passing them to SDK methods are not affected. Validated UUIDs round-trip through the SDK request path unchanged. Impact
Patches / mitigationThe SDK now applies path-segment encoding to identifier values before they are interpolated into request URL templates. After this change, identifier values that contain characters with special meaning in URL paths are transmitted as encoded byte sequences and routed to the resource the SDK method's call site indicates. CompatibilityIdentifier values that match the standard UUID format, or any other format that contains only characters safe to transmit unencoded in URL path segments, round-trip through the SDK request path unchanged. Applications that already validate identifier inputs see no behavioral change. Operational guidance
LangSmith / hosted deployments noteThis issue affects the SDK that runs in caller applications. The LangGraph server runtime, including LangSmith-hosted deployments, receives ordinary HTTP requests on documented routes and is not itself affected by this issue. Applications that consume LangSmith-hosted services via First reported by: pucagit (CyStack). Affected versions
0.1.0
0.1.1
0.1.10
0.1.11
0.1.12
0.1.14
0.1.16
0.1.17
0.1.18
0.1.2
0.1.20
0.1.21
+ 84 more Show less
0.1.22
0.1.23
0.1.24
0.1.25
0.1.26
0.1.27
0.1.28
0.1.29
0.1.3
0.1.30
0.1.31
0.1.32
0.1.33
0.1.34
0.1.35
0.1.36
0.1.37
0.1.38
0.1.39
0.1.4
0.1.40
0.1.42
0.1.43
0.1.44
0.1.45
0.1.46
0.1.47
0.1.48
0.1.5
0.1.50
0.1.51
0.1.53
0.1.55
0.1.56
0.1.57
0.1.58
0.1.59
0.1.6
0.1.60
0.1.61
0.1.62
0.1.63
0.1.64
0.1.65
0.1.66
0.1.69
0.1.7
0.1.70
0.1.71
0.1.72
0.1.73
0.1.74
0.1.8
0.1.9
0.2.0
0.2.0a1
0.2.1
0.2.10
0.2.12
0.2.14
0.2.15
0.2.2
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.10
0.3.11
0.3.12
0.3.13
0.3.14
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.3.8
0.3.9
Fixed in
0.3.15
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.3.3
patch
1 CVE
CVE-2026-48776
PYSEC-2026-2575
GHSA-w39p-vh2g-g8g5
PYSEC-2026-2194
Jul 13, 2026
LangGraph SDK has unsafe URL path construction
4.2
/ 10
Medium
Network
High
Low
None
Unchanged
Low
Low
None
Summary
This issue is most consequential in deployments that:
There have no evidence of this behavior being triggered in the wild. This change is intended to reduce the surface available when caller-supplied identifier values originate from untrusted sources. Affected users / systemsYou may be affected if you:
Applications that validate identifier values (for example, by parsing them as UUIDs and rejecting anything that does not parse) before passing them to SDK methods are not affected. Validated UUIDs round-trip through the SDK request path unchanged. Impact
Patches / mitigationThe SDK now applies path-segment encoding to identifier values before they are interpolated into request URL templates. After this change, identifier values that contain characters with special meaning in URL paths are transmitted as encoded byte sequences and routed to the resource the SDK method's call site indicates. CompatibilityIdentifier values that match the standard UUID format, or any other format that contains only characters safe to transmit unencoded in URL path segments, round-trip through the SDK request path unchanged. Applications that already validate identifier inputs see no behavioral change. Operational guidance
LangSmith / hosted deployments noteThis issue affects the SDK that runs in caller applications. The LangGraph server runtime, including LangSmith-hosted deployments, receives ordinary HTTP requests on documented routes and is not itself affected by this issue. Applications that consume LangSmith-hosted services via First reported by: pucagit (CyStack). Affected versions
0.1.0
0.1.1
0.1.10
0.1.11
0.1.12
0.1.14
0.1.16
0.1.17
0.1.18
0.1.2
0.1.20
0.1.21
+ 84 more Show less
0.1.22
0.1.23
0.1.24
0.1.25
0.1.26
0.1.27
0.1.28
0.1.29
0.1.3
0.1.30
0.1.31
0.1.32
0.1.33
0.1.34
0.1.35
0.1.36
0.1.37
0.1.38
0.1.39
0.1.4
0.1.40
0.1.42
0.1.43
0.1.44
0.1.45
0.1.46
0.1.47
0.1.48
0.1.5
0.1.50
0.1.51
0.1.53
0.1.55
0.1.56
0.1.57
0.1.58
0.1.59
0.1.6
0.1.60
0.1.61
0.1.62
0.1.63
0.1.64
0.1.65
0.1.66
0.1.69
0.1.7
0.1.70
0.1.71
0.1.72
0.1.73
0.1.74
0.1.8
0.1.9
0.2.0
0.2.0a1
0.2.1
0.2.10
0.2.12
0.2.14
0.2.15
0.2.2
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.10
0.3.11
0.3.12
0.3.13
0.3.14
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.3.8
0.3.9
Fixed in
0.3.15
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.3.2
patch
1 CVE
CVE-2026-48776
PYSEC-2026-2575
GHSA-w39p-vh2g-g8g5
PYSEC-2026-2194
Jul 13, 2026
LangGraph SDK has unsafe URL path construction
4.2
/ 10
Medium
Network
High
Low
None
Unchanged
Low
Low
None
Summary
This issue is most consequential in deployments that:
There have no evidence of this behavior being triggered in the wild. This change is intended to reduce the surface available when caller-supplied identifier values originate from untrusted sources. Affected users / systemsYou may be affected if you:
Applications that validate identifier values (for example, by parsing them as UUIDs and rejecting anything that does not parse) before passing them to SDK methods are not affected. Validated UUIDs round-trip through the SDK request path unchanged. Impact
Patches / mitigationThe SDK now applies path-segment encoding to identifier values before they are interpolated into request URL templates. After this change, identifier values that contain characters with special meaning in URL paths are transmitted as encoded byte sequences and routed to the resource the SDK method's call site indicates. CompatibilityIdentifier values that match the standard UUID format, or any other format that contains only characters safe to transmit unencoded in URL path segments, round-trip through the SDK request path unchanged. Applications that already validate identifier inputs see no behavioral change. Operational guidance
LangSmith / hosted deployments noteThis issue affects the SDK that runs in caller applications. The LangGraph server runtime, including LangSmith-hosted deployments, receives ordinary HTTP requests on documented routes and is not itself affected by this issue. Applications that consume LangSmith-hosted services via First reported by: pucagit (CyStack). Affected versions
0.1.0
0.1.1
0.1.10
0.1.11
0.1.12
0.1.14
0.1.16
0.1.17
0.1.18
0.1.2
0.1.20
0.1.21
+ 84 more Show less
0.1.22
0.1.23
0.1.24
0.1.25
0.1.26
0.1.27
0.1.28
0.1.29
0.1.3
0.1.30
0.1.31
0.1.32
0.1.33
0.1.34
0.1.35
0.1.36
0.1.37
0.1.38
0.1.39
0.1.4
0.1.40
0.1.42
0.1.43
0.1.44
0.1.45
0.1.46
0.1.47
0.1.48
0.1.5
0.1.50
0.1.51
0.1.53
0.1.55
0.1.56
0.1.57
0.1.58
0.1.59
0.1.6
0.1.60
0.1.61
0.1.62
0.1.63
0.1.64
0.1.65
0.1.66
0.1.69
0.1.7
0.1.70
0.1.71
0.1.72
0.1.73
0.1.74
0.1.8
0.1.9
0.2.0
0.2.0a1
0.2.1
0.2.10
0.2.12
0.2.14
0.2.15
0.2.2
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.10
0.3.11
0.3.12
0.3.13
0.3.14
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.3.8
0.3.9
Fixed in
0.3.15
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.3.1
patch
1 CVE
CVE-2026-48776
PYSEC-2026-2575
GHSA-w39p-vh2g-g8g5
PYSEC-2026-2194
Jul 13, 2026
LangGraph SDK has unsafe URL path construction
4.2
/ 10
Medium
Network
High
Low
None
Unchanged
Low
Low
None
Summary
This issue is most consequential in deployments that:
There have no evidence of this behavior being triggered in the wild. This change is intended to reduce the surface available when caller-supplied identifier values originate from untrusted sources. Affected users / systemsYou may be affected if you:
Applications that validate identifier values (for example, by parsing them as UUIDs and rejecting anything that does not parse) before passing them to SDK methods are not affected. Validated UUIDs round-trip through the SDK request path unchanged. Impact
Patches / mitigationThe SDK now applies path-segment encoding to identifier values before they are interpolated into request URL templates. After this change, identifier values that contain characters with special meaning in URL paths are transmitted as encoded byte sequences and routed to the resource the SDK method's call site indicates. CompatibilityIdentifier values that match the standard UUID format, or any other format that contains only characters safe to transmit unencoded in URL path segments, round-trip through the SDK request path unchanged. Applications that already validate identifier inputs see no behavioral change. Operational guidance
LangSmith / hosted deployments noteThis issue affects the SDK that runs in caller applications. The LangGraph server runtime, including LangSmith-hosted deployments, receives ordinary HTTP requests on documented routes and is not itself affected by this issue. Applications that consume LangSmith-hosted services via First reported by: pucagit (CyStack). Affected versions
0.1.0
0.1.1
0.1.10
0.1.11
0.1.12
0.1.14
0.1.16
0.1.17
0.1.18
0.1.2
0.1.20
0.1.21
+ 84 more Show less
0.1.22
0.1.23
0.1.24
0.1.25
0.1.26
0.1.27
0.1.28
0.1.29
0.1.3
0.1.30
0.1.31
0.1.32
0.1.33
0.1.34
0.1.35
0.1.36
0.1.37
0.1.38
0.1.39
0.1.4
0.1.40
0.1.42
0.1.43
0.1.44
0.1.45
0.1.46
0.1.47
0.1.48
0.1.5
0.1.50
0.1.51
0.1.53
0.1.55
0.1.56
0.1.57
0.1.58
0.1.59
0.1.6
0.1.60
0.1.61
0.1.62
0.1.63
0.1.64
0.1.65
0.1.66
0.1.69
0.1.7
0.1.70
0.1.71
0.1.72
0.1.73
0.1.74
0.1.8
0.1.9
0.2.0
0.2.0a1
0.2.1
0.2.10
0.2.12
0.2.14
0.2.15
0.2.2
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.10
0.3.11
0.3.12
0.3.13
0.3.14
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.3.8
0.3.9
Fixed in
0.3.15
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.3.0
minor
1 CVE
CVE-2026-48776
PYSEC-2026-2575
GHSA-w39p-vh2g-g8g5
PYSEC-2026-2194
Jul 13, 2026
LangGraph SDK has unsafe URL path construction
4.2
/ 10
Medium
Network
High
Low
None
Unchanged
Low
Low
None
Summary
This issue is most consequential in deployments that:
There have no evidence of this behavior being triggered in the wild. This change is intended to reduce the surface available when caller-supplied identifier values originate from untrusted sources. Affected users / systemsYou may be affected if you:
Applications that validate identifier values (for example, by parsing them as UUIDs and rejecting anything that does not parse) before passing them to SDK methods are not affected. Validated UUIDs round-trip through the SDK request path unchanged. Impact
Patches / mitigationThe SDK now applies path-segment encoding to identifier values before they are interpolated into request URL templates. After this change, identifier values that contain characters with special meaning in URL paths are transmitted as encoded byte sequences and routed to the resource the SDK method's call site indicates. CompatibilityIdentifier values that match the standard UUID format, or any other format that contains only characters safe to transmit unencoded in URL path segments, round-trip through the SDK request path unchanged. Applications that already validate identifier inputs see no behavioral change. Operational guidance
LangSmith / hosted deployments noteThis issue affects the SDK that runs in caller applications. The LangGraph server runtime, including LangSmith-hosted deployments, receives ordinary HTTP requests on documented routes and is not itself affected by this issue. Applications that consume LangSmith-hosted services via First reported by: pucagit (CyStack). Affected versions
0.1.0
0.1.1
0.1.10
0.1.11
0.1.12
0.1.14
0.1.16
0.1.17
0.1.18
0.1.2
0.1.20
0.1.21
+ 84 more Show less
0.1.22
0.1.23
0.1.24
0.1.25
0.1.26
0.1.27
0.1.28
0.1.29
0.1.3
0.1.30
0.1.31
0.1.32
0.1.33
0.1.34
0.1.35
0.1.36
0.1.37
0.1.38
0.1.39
0.1.4
0.1.40
0.1.42
0.1.43
0.1.44
0.1.45
0.1.46
0.1.47
0.1.48
0.1.5
0.1.50
0.1.51
0.1.53
0.1.55
0.1.56
0.1.57
0.1.58
0.1.59
0.1.6
0.1.60
0.1.61
0.1.62
0.1.63
0.1.64
0.1.65
0.1.66
0.1.69
0.1.7
0.1.70
0.1.71
0.1.72
0.1.73
0.1.74
0.1.8
0.1.9
0.2.0
0.2.0a1
0.2.1
0.2.10
0.2.12
0.2.14
0.2.15
0.2.2
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.10
0.3.11
0.3.12
0.3.13
0.3.14
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.3.8
0.3.9
Fixed in
0.3.15
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.2.15
patch
1 CVE
CVE-2026-48776
PYSEC-2026-2575
GHSA-w39p-vh2g-g8g5
PYSEC-2026-2194
Jul 13, 2026
LangGraph SDK has unsafe URL path construction
4.2
/ 10
Medium
Network
High
Low
None
Unchanged
Low
Low
None
Summary
This issue is most consequential in deployments that:
There have no evidence of this behavior being triggered in the wild. This change is intended to reduce the surface available when caller-supplied identifier values originate from untrusted sources. Affected users / systemsYou may be affected if you:
Applications that validate identifier values (for example, by parsing them as UUIDs and rejecting anything that does not parse) before passing them to SDK methods are not affected. Validated UUIDs round-trip through the SDK request path unchanged. Impact
Patches / mitigationThe SDK now applies path-segment encoding to identifier values before they are interpolated into request URL templates. After this change, identifier values that contain characters with special meaning in URL paths are transmitted as encoded byte sequences and routed to the resource the SDK method's call site indicates. CompatibilityIdentifier values that match the standard UUID format, or any other format that contains only characters safe to transmit unencoded in URL path segments, round-trip through the SDK request path unchanged. Applications that already validate identifier inputs see no behavioral change. Operational guidance
LangSmith / hosted deployments noteThis issue affects the SDK that runs in caller applications. The LangGraph server runtime, including LangSmith-hosted deployments, receives ordinary HTTP requests on documented routes and is not itself affected by this issue. Applications that consume LangSmith-hosted services via First reported by: pucagit (CyStack). Affected versions
0.1.0
0.1.1
0.1.10
0.1.11
0.1.12
0.1.14
0.1.16
0.1.17
0.1.18
0.1.2
0.1.20
0.1.21
+ 84 more Show less
0.1.22
0.1.23
0.1.24
0.1.25
0.1.26
0.1.27
0.1.28
0.1.29
0.1.3
0.1.30
0.1.31
0.1.32
0.1.33
0.1.34
0.1.35
0.1.36
0.1.37
0.1.38
0.1.39
0.1.4
0.1.40
0.1.42
0.1.43
0.1.44
0.1.45
0.1.46
0.1.47
0.1.48
0.1.5
0.1.50
0.1.51
0.1.53
0.1.55
0.1.56
0.1.57
0.1.58
0.1.59
0.1.6
0.1.60
0.1.61
0.1.62
0.1.63
0.1.64
0.1.65
0.1.66
0.1.69
0.1.7
0.1.70
0.1.71
0.1.72
0.1.73
0.1.74
0.1.8
0.1.9
0.2.0
0.2.0a1
0.2.1
0.2.10
0.2.12
0.2.14
0.2.15
0.2.2
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.10
0.3.11
0.3.12
0.3.13
0.3.14
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.3.8
0.3.9
Fixed in
0.3.15
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.2.14
patch
1 CVE
CVE-2026-48776
PYSEC-2026-2575
GHSA-w39p-vh2g-g8g5
PYSEC-2026-2194
Jul 13, 2026
LangGraph SDK has unsafe URL path construction
4.2
/ 10
Medium
Network
High
Low
None
Unchanged
Low
Low
None
Summary
This issue is most consequential in deployments that:
There have no evidence of this behavior being triggered in the wild. This change is intended to reduce the surface available when caller-supplied identifier values originate from untrusted sources. Affected users / systemsYou may be affected if you:
Applications that validate identifier values (for example, by parsing them as UUIDs and rejecting anything that does not parse) before passing them to SDK methods are not affected. Validated UUIDs round-trip through the SDK request path unchanged. Impact
Patches / mitigationThe SDK now applies path-segment encoding to identifier values before they are interpolated into request URL templates. After this change, identifier values that contain characters with special meaning in URL paths are transmitted as encoded byte sequences and routed to the resource the SDK method's call site indicates. CompatibilityIdentifier values that match the standard UUID format, or any other format that contains only characters safe to transmit unencoded in URL path segments, round-trip through the SDK request path unchanged. Applications that already validate identifier inputs see no behavioral change. Operational guidance
LangSmith / hosted deployments noteThis issue affects the SDK that runs in caller applications. The LangGraph server runtime, including LangSmith-hosted deployments, receives ordinary HTTP requests on documented routes and is not itself affected by this issue. Applications that consume LangSmith-hosted services via First reported by: pucagit (CyStack). Affected versions
0.1.0
0.1.1
0.1.10
0.1.11
0.1.12
0.1.14
0.1.16
0.1.17
0.1.18
0.1.2
0.1.20
0.1.21
+ 84 more Show less
0.1.22
0.1.23
0.1.24
0.1.25
0.1.26
0.1.27
0.1.28
0.1.29
0.1.3
0.1.30
0.1.31
0.1.32
0.1.33
0.1.34
0.1.35
0.1.36
0.1.37
0.1.38
0.1.39
0.1.4
0.1.40
0.1.42
0.1.43
0.1.44
0.1.45
0.1.46
0.1.47
0.1.48
0.1.5
0.1.50
0.1.51
0.1.53
0.1.55
0.1.56
0.1.57
0.1.58
0.1.59
0.1.6
0.1.60
0.1.61
0.1.62
0.1.63
0.1.64
0.1.65
0.1.66
0.1.69
0.1.7
0.1.70
0.1.71
0.1.72
0.1.73
0.1.74
0.1.8
0.1.9
0.2.0
0.2.0a1
0.2.1
0.2.10
0.2.12
0.2.14
0.2.15
0.2.2
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.10
0.3.11
0.3.12
0.3.13
0.3.14
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.3.8
0.3.9
Fixed in
0.3.15
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.2.12
patch
1 CVE
CVE-2026-48776
PYSEC-2026-2575
GHSA-w39p-vh2g-g8g5
PYSEC-2026-2194
Jul 13, 2026
LangGraph SDK has unsafe URL path construction
4.2
/ 10
Medium
Network
High
Low
None
Unchanged
Low
Low
None
Summary
This issue is most consequential in deployments that:
There have no evidence of this behavior being triggered in the wild. This change is intended to reduce the surface available when caller-supplied identifier values originate from untrusted sources. Affected users / systemsYou may be affected if you:
Applications that validate identifier values (for example, by parsing them as UUIDs and rejecting anything that does not parse) before passing them to SDK methods are not affected. Validated UUIDs round-trip through the SDK request path unchanged. Impact
Patches / mitigationThe SDK now applies path-segment encoding to identifier values before they are interpolated into request URL templates. After this change, identifier values that contain characters with special meaning in URL paths are transmitted as encoded byte sequences and routed to the resource the SDK method's call site indicates. CompatibilityIdentifier values that match the standard UUID format, or any other format that contains only characters safe to transmit unencoded in URL path segments, round-trip through the SDK request path unchanged. Applications that already validate identifier inputs see no behavioral change. Operational guidance
LangSmith / hosted deployments noteThis issue affects the SDK that runs in caller applications. The LangGraph server runtime, including LangSmith-hosted deployments, receives ordinary HTTP requests on documented routes and is not itself affected by this issue. Applications that consume LangSmith-hosted services via First reported by: pucagit (CyStack). Affected versions
0.1.0
0.1.1
0.1.10
0.1.11
0.1.12
0.1.14
0.1.16
0.1.17
0.1.18
0.1.2
0.1.20
0.1.21
+ 84 more Show less
0.1.22
0.1.23
0.1.24
0.1.25
0.1.26
0.1.27
0.1.28
0.1.29
0.1.3
0.1.30
0.1.31
0.1.32
0.1.33
0.1.34
0.1.35
0.1.36
0.1.37
0.1.38
0.1.39
0.1.4
0.1.40
0.1.42
0.1.43
0.1.44
0.1.45
0.1.46
0.1.47
0.1.48
0.1.5
0.1.50
0.1.51
0.1.53
0.1.55
0.1.56
0.1.57
0.1.58
0.1.59
0.1.6
0.1.60
0.1.61
0.1.62
0.1.63
0.1.64
0.1.65
0.1.66
0.1.69
0.1.7
0.1.70
0.1.71
0.1.72
0.1.73
0.1.74
0.1.8
0.1.9
0.2.0
0.2.0a1
0.2.1
0.2.10
0.2.12
0.2.14
0.2.15
0.2.2
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.10
0.3.11
0.3.12
0.3.13
0.3.14
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.3.8
0.3.9
Fixed in
0.3.15
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.2.10
patch
1 CVE
CVE-2026-48776
PYSEC-2026-2575
GHSA-w39p-vh2g-g8g5
PYSEC-2026-2194
Jul 13, 2026
LangGraph SDK has unsafe URL path construction
4.2
/ 10
Medium
Network
High
Low
None
Unchanged
Low
Low
None
Summary
This issue is most consequential in deployments that:
There have no evidence of this behavior being triggered in the wild. This change is intended to reduce the surface available when caller-supplied identifier values originate from untrusted sources. Affected users / systemsYou may be affected if you:
Applications that validate identifier values (for example, by parsing them as UUIDs and rejecting anything that does not parse) before passing them to SDK methods are not affected. Validated UUIDs round-trip through the SDK request path unchanged. Impact
Patches / mitigationThe SDK now applies path-segment encoding to identifier values before they are interpolated into request URL templates. After this change, identifier values that contain characters with special meaning in URL paths are transmitted as encoded byte sequences and routed to the resource the SDK method's call site indicates. CompatibilityIdentifier values that match the standard UUID format, or any other format that contains only characters safe to transmit unencoded in URL path segments, round-trip through the SDK request path unchanged. Applications that already validate identifier inputs see no behavioral change. Operational guidance
LangSmith / hosted deployments noteThis issue affects the SDK that runs in caller applications. The LangGraph server runtime, including LangSmith-hosted deployments, receives ordinary HTTP requests on documented routes and is not itself affected by this issue. Applications that consume LangSmith-hosted services via First reported by: pucagit (CyStack). Affected versions
0.1.0
0.1.1
0.1.10
0.1.11
0.1.12
0.1.14
0.1.16
0.1.17
0.1.18
0.1.2
0.1.20
0.1.21
+ 84 more Show less
0.1.22
0.1.23
0.1.24
0.1.25
0.1.26
0.1.27
0.1.28
0.1.29
0.1.3
0.1.30
0.1.31
0.1.32
0.1.33
0.1.34
0.1.35
0.1.36
0.1.37
0.1.38
0.1.39
0.1.4
0.1.40
0.1.42
0.1.43
0.1.44
0.1.45
0.1.46
0.1.47
0.1.48
0.1.5
0.1.50
0.1.51
0.1.53
0.1.55
0.1.56
0.1.57
0.1.58
0.1.59
0.1.6
0.1.60
0.1.61
0.1.62
0.1.63
0.1.64
0.1.65
0.1.66
0.1.69
0.1.7
0.1.70
0.1.71
0.1.72
0.1.73
0.1.74
0.1.8
0.1.9
0.2.0
0.2.0a1
0.2.1
0.2.10
0.2.12
0.2.14
0.2.15
0.2.2
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.10
0.3.11
0.3.12
0.3.13
0.3.14
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.3.8
0.3.9
Fixed in
0.3.15
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.2.9
patch
1 CVE
CVE-2026-48776
PYSEC-2026-2575
GHSA-w39p-vh2g-g8g5
PYSEC-2026-2194
Jul 13, 2026
LangGraph SDK has unsafe URL path construction
4.2
/ 10
Medium
Network
High
Low
None
Unchanged
Low
Low
None
Summary
This issue is most consequential in deployments that:
There have no evidence of this behavior being triggered in the wild. This change is intended to reduce the surface available when caller-supplied identifier values originate from untrusted sources. Affected users / systemsYou may be affected if you:
Applications that validate identifier values (for example, by parsing them as UUIDs and rejecting anything that does not parse) before passing them to SDK methods are not affected. Validated UUIDs round-trip through the SDK request path unchanged. Impact
Patches / mitigationThe SDK now applies path-segment encoding to identifier values before they are interpolated into request URL templates. After this change, identifier values that contain characters with special meaning in URL paths are transmitted as encoded byte sequences and routed to the resource the SDK method's call site indicates. CompatibilityIdentifier values that match the standard UUID format, or any other format that contains only characters safe to transmit unencoded in URL path segments, round-trip through the SDK request path unchanged. Applications that already validate identifier inputs see no behavioral change. Operational guidance
LangSmith / hosted deployments noteThis issue affects the SDK that runs in caller applications. The LangGraph server runtime, including LangSmith-hosted deployments, receives ordinary HTTP requests on documented routes and is not itself affected by this issue. Applications that consume LangSmith-hosted services via First reported by: pucagit (CyStack). Affected versions
0.1.0
0.1.1
0.1.10
0.1.11
0.1.12
0.1.14
0.1.16
0.1.17
0.1.18
0.1.2
0.1.20
0.1.21
+ 84 more Show less
0.1.22
0.1.23
0.1.24
0.1.25
0.1.26
0.1.27
0.1.28
0.1.29
0.1.3
0.1.30
0.1.31
0.1.32
0.1.33
0.1.34
0.1.35
0.1.36
0.1.37
0.1.38
0.1.39
0.1.4
0.1.40
0.1.42
0.1.43
0.1.44
0.1.45
0.1.46
0.1.47
0.1.48
0.1.5
0.1.50
0.1.51
0.1.53
0.1.55
0.1.56
0.1.57
0.1.58
0.1.59
0.1.6
0.1.60
0.1.61
0.1.62
0.1.63
0.1.64
0.1.65
0.1.66
0.1.69
0.1.7
0.1.70
0.1.71
0.1.72
0.1.73
0.1.74
0.1.8
0.1.9
0.2.0
0.2.0a1
0.2.1
0.2.10
0.2.12
0.2.14
0.2.15
0.2.2
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.10
0.3.11
0.3.12
0.3.13
0.3.14
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.3.8
0.3.9
Fixed in
0.3.15
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.2.8
patch
1 CVE
CVE-2026-48776
PYSEC-2026-2575
GHSA-w39p-vh2g-g8g5
PYSEC-2026-2194
Jul 13, 2026
LangGraph SDK has unsafe URL path construction
4.2
/ 10
Medium
Network
High
Low
None
Unchanged
Low
Low
None
Summary
This issue is most consequential in deployments that:
There have no evidence of this behavior being triggered in the wild. This change is intended to reduce the surface available when caller-supplied identifier values originate from untrusted sources. Affected users / systemsYou may be affected if you:
Applications that validate identifier values (for example, by parsing them as UUIDs and rejecting anything that does not parse) before passing them to SDK methods are not affected. Validated UUIDs round-trip through the SDK request path unchanged. Impact
Patches / mitigationThe SDK now applies path-segment encoding to identifier values before they are interpolated into request URL templates. After this change, identifier values that contain characters with special meaning in URL paths are transmitted as encoded byte sequences and routed to the resource the SDK method's call site indicates. CompatibilityIdentifier values that match the standard UUID format, or any other format that contains only characters safe to transmit unencoded in URL path segments, round-trip through the SDK request path unchanged. Applications that already validate identifier inputs see no behavioral change. Operational guidance
LangSmith / hosted deployments noteThis issue affects the SDK that runs in caller applications. The LangGraph server runtime, including LangSmith-hosted deployments, receives ordinary HTTP requests on documented routes and is not itself affected by this issue. Applications that consume LangSmith-hosted services via First reported by: pucagit (CyStack). Affected versions
0.1.0
0.1.1
0.1.10
0.1.11
0.1.12
0.1.14
0.1.16
0.1.17
0.1.18
0.1.2
0.1.20
0.1.21
+ 84 more Show less
0.1.22
0.1.23
0.1.24
0.1.25
0.1.26
0.1.27
0.1.28
0.1.29
0.1.3
0.1.30
0.1.31
0.1.32
0.1.33
0.1.34
0.1.35
0.1.36
0.1.37
0.1.38
0.1.39
0.1.4
0.1.40
0.1.42
0.1.43
0.1.44
0.1.45
0.1.46
0.1.47
0.1.48
0.1.5
0.1.50
0.1.51
0.1.53
0.1.55
0.1.56
0.1.57
0.1.58
0.1.59
0.1.6
0.1.60
0.1.61
0.1.62
0.1.63
0.1.64
0.1.65
0.1.66
0.1.69
0.1.7
0.1.70
0.1.71
0.1.72
0.1.73
0.1.74
0.1.8
0.1.9
0.2.0
0.2.0a1
0.2.1
0.2.10
0.2.12
0.2.14
0.2.15
0.2.2
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.10
0.3.11
0.3.12
0.3.13
0.3.14
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.3.8
0.3.9
Fixed in
0.3.15
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.2.7
patch
1 CVE
CVE-2026-48776
PYSEC-2026-2575
GHSA-w39p-vh2g-g8g5
PYSEC-2026-2194
Jul 13, 2026
LangGraph SDK has unsafe URL path construction
4.2
/ 10
Medium
Network
High
Low
None
Unchanged
Low
Low
None
Summary
This issue is most consequential in deployments that:
There have no evidence of this behavior being triggered in the wild. This change is intended to reduce the surface available when caller-supplied identifier values originate from untrusted sources. Affected users / systemsYou may be affected if you:
Applications that validate identifier values (for example, by parsing them as UUIDs and rejecting anything that does not parse) before passing them to SDK methods are not affected. Validated UUIDs round-trip through the SDK request path unchanged. Impact
Patches / mitigationThe SDK now applies path-segment encoding to identifier values before they are interpolated into request URL templates. After this change, identifier values that contain characters with special meaning in URL paths are transmitted as encoded byte sequences and routed to the resource the SDK method's call site indicates. CompatibilityIdentifier values that match the standard UUID format, or any other format that contains only characters safe to transmit unencoded in URL path segments, round-trip through the SDK request path unchanged. Applications that already validate identifier inputs see no behavioral change. Operational guidance
LangSmith / hosted deployments noteThis issue affects the SDK that runs in caller applications. The LangGraph server runtime, including LangSmith-hosted deployments, receives ordinary HTTP requests on documented routes and is not itself affected by this issue. Applications that consume LangSmith-hosted services via First reported by: pucagit (CyStack). Affected versions
0.1.0
0.1.1
0.1.10
0.1.11
0.1.12
0.1.14
0.1.16
0.1.17
0.1.18
0.1.2
0.1.20
0.1.21
+ 84 more Show less
0.1.22
0.1.23
0.1.24
0.1.25
0.1.26
0.1.27
0.1.28
0.1.29
0.1.3
0.1.30
0.1.31
0.1.32
0.1.33
0.1.34
0.1.35
0.1.36
0.1.37
0.1.38
0.1.39
0.1.4
0.1.40
0.1.42
0.1.43
0.1.44
0.1.45
0.1.46
0.1.47
0.1.48
0.1.5
0.1.50
0.1.51
0.1.53
0.1.55
0.1.56
0.1.57
0.1.58
0.1.59
0.1.6
0.1.60
0.1.61
0.1.62
0.1.63
0.1.64
0.1.65
0.1.66
0.1.69
0.1.7
0.1.70
0.1.71
0.1.72
0.1.73
0.1.74
0.1.8
0.1.9
0.2.0
0.2.0a1
0.2.1
0.2.10
0.2.12
0.2.14
0.2.15
0.2.2
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.10
0.3.11
0.3.12
0.3.13
0.3.14
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.3.8
0.3.9
Fixed in
0.3.15
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.2.6
patch
1 CVE
CVE-2026-48776
PYSEC-2026-2575
GHSA-w39p-vh2g-g8g5
PYSEC-2026-2194
Jul 13, 2026
LangGraph SDK has unsafe URL path construction
4.2
/ 10
Medium
Network
High
Low
None
Unchanged
Low
Low
None
Summary
This issue is most consequential in deployments that:
There have no evidence of this behavior being triggered in the wild. This change is intended to reduce the surface available when caller-supplied identifier values originate from untrusted sources. Affected users / systemsYou may be affected if you:
Applications that validate identifier values (for example, by parsing them as UUIDs and rejecting anything that does not parse) before passing them to SDK methods are not affected. Validated UUIDs round-trip through the SDK request path unchanged. Impact
Patches / mitigationThe SDK now applies path-segment encoding to identifier values before they are interpolated into request URL templates. After this change, identifier values that contain characters with special meaning in URL paths are transmitted as encoded byte sequences and routed to the resource the SDK method's call site indicates. CompatibilityIdentifier values that match the standard UUID format, or any other format that contains only characters safe to transmit unencoded in URL path segments, round-trip through the SDK request path unchanged. Applications that already validate identifier inputs see no behavioral change. Operational guidance
LangSmith / hosted deployments noteThis issue affects the SDK that runs in caller applications. The LangGraph server runtime, including LangSmith-hosted deployments, receives ordinary HTTP requests on documented routes and is not itself affected by this issue. Applications that consume LangSmith-hosted services via First reported by: pucagit (CyStack). Affected versions
0.1.0
0.1.1
0.1.10
0.1.11
0.1.12
0.1.14
0.1.16
0.1.17
0.1.18
0.1.2
0.1.20
0.1.21
+ 84 more Show less
0.1.22
0.1.23
0.1.24
0.1.25
0.1.26
0.1.27
0.1.28
0.1.29
0.1.3
0.1.30
0.1.31
0.1.32
0.1.33
0.1.34
0.1.35
0.1.36
0.1.37
0.1.38
0.1.39
0.1.4
0.1.40
0.1.42
0.1.43
0.1.44
0.1.45
0.1.46
0.1.47
0.1.48
0.1.5
0.1.50
0.1.51
0.1.53
0.1.55
0.1.56
0.1.57
0.1.58
0.1.59
0.1.6
0.1.60
0.1.61
0.1.62
0.1.63
0.1.64
0.1.65
0.1.66
0.1.69
0.1.7
0.1.70
0.1.71
0.1.72
0.1.73
0.1.74
0.1.8
0.1.9
0.2.0
0.2.0a1
0.2.1
0.2.10
0.2.12
0.2.14
0.2.15
0.2.2
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.10
0.3.11
0.3.12
0.3.13
0.3.14
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.3.8
0.3.9
Fixed in
0.3.15
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.2.5
patch
1 CVE
CVE-2026-48776
PYSEC-2026-2575
GHSA-w39p-vh2g-g8g5
PYSEC-2026-2194
Jul 13, 2026
LangGraph SDK has unsafe URL path construction
4.2
/ 10
Medium
Network
High
Low
None
Unchanged
Low
Low
None
Summary
This issue is most consequential in deployments that:
There have no evidence of this behavior being triggered in the wild. This change is intended to reduce the surface available when caller-supplied identifier values originate from untrusted sources. Affected users / systemsYou may be affected if you:
Applications that validate identifier values (for example, by parsing them as UUIDs and rejecting anything that does not parse) before passing them to SDK methods are not affected. Validated UUIDs round-trip through the SDK request path unchanged. Impact
Patches / mitigationThe SDK now applies path-segment encoding to identifier values before they are interpolated into request URL templates. After this change, identifier values that contain characters with special meaning in URL paths are transmitted as encoded byte sequences and routed to the resource the SDK method's call site indicates. CompatibilityIdentifier values that match the standard UUID format, or any other format that contains only characters safe to transmit unencoded in URL path segments, round-trip through the SDK request path unchanged. Applications that already validate identifier inputs see no behavioral change. Operational guidance
LangSmith / hosted deployments noteThis issue affects the SDK that runs in caller applications. The LangGraph server runtime, including LangSmith-hosted deployments, receives ordinary HTTP requests on documented routes and is not itself affected by this issue. Applications that consume LangSmith-hosted services via First reported by: pucagit (CyStack). Affected versions
0.1.0
0.1.1
0.1.10
0.1.11
0.1.12
0.1.14
0.1.16
0.1.17
0.1.18
0.1.2
0.1.20
0.1.21
+ 84 more Show less
0.1.22
0.1.23
0.1.24
0.1.25
0.1.26
0.1.27
0.1.28
0.1.29
0.1.3
0.1.30
0.1.31
0.1.32
0.1.33
0.1.34
0.1.35
0.1.36
0.1.37
0.1.38
0.1.39
0.1.4
0.1.40
0.1.42
0.1.43
0.1.44
0.1.45
0.1.46
0.1.47
0.1.48
0.1.5
0.1.50
0.1.51
0.1.53
0.1.55
0.1.56
0.1.57
0.1.58
0.1.59
0.1.6
0.1.60
0.1.61
0.1.62
0.1.63
0.1.64
0.1.65
0.1.66
0.1.69
0.1.7
0.1.70
0.1.71
0.1.72
0.1.73
0.1.74
0.1.8
0.1.9
0.2.0
0.2.0a1
0.2.1
0.2.10
0.2.12
0.2.14
0.2.15
0.2.2
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.10
0.3.11
0.3.12
0.3.13
0.3.14
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.3.8
0.3.9
Fixed in
0.3.15
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.2.4
patch
1 CVE
CVE-2026-48776
PYSEC-2026-2575
GHSA-w39p-vh2g-g8g5
PYSEC-2026-2194
Jul 13, 2026
LangGraph SDK has unsafe URL path construction
4.2
/ 10
Medium
Network
High
Low
None
Unchanged
Low
Low
None
Summary
This issue is most consequential in deployments that:
There have no evidence of this behavior being triggered in the wild. This change is intended to reduce the surface available when caller-supplied identifier values originate from untrusted sources. Affected users / systemsYou may be affected if you:
Applications that validate identifier values (for example, by parsing them as UUIDs and rejecting anything that does not parse) before passing them to SDK methods are not affected. Validated UUIDs round-trip through the SDK request path unchanged. Impact
Patches / mitigationThe SDK now applies path-segment encoding to identifier values before they are interpolated into request URL templates. After this change, identifier values that contain characters with special meaning in URL paths are transmitted as encoded byte sequences and routed to the resource the SDK method's call site indicates. CompatibilityIdentifier values that match the standard UUID format, or any other format that contains only characters safe to transmit unencoded in URL path segments, round-trip through the SDK request path unchanged. Applications that already validate identifier inputs see no behavioral change. Operational guidance
LangSmith / hosted deployments noteThis issue affects the SDK that runs in caller applications. The LangGraph server runtime, including LangSmith-hosted deployments, receives ordinary HTTP requests on documented routes and is not itself affected by this issue. Applications that consume LangSmith-hosted services via First reported by: pucagit (CyStack). Affected versions
0.1.0
0.1.1
0.1.10
0.1.11
0.1.12
0.1.14
0.1.16
0.1.17
0.1.18
0.1.2
0.1.20
0.1.21
+ 84 more Show less
0.1.22
0.1.23
0.1.24
0.1.25
0.1.26
0.1.27
0.1.28
0.1.29
0.1.3
0.1.30
0.1.31
0.1.32
0.1.33
0.1.34
0.1.35
0.1.36
0.1.37
0.1.38
0.1.39
0.1.4
0.1.40
0.1.42
0.1.43
0.1.44
0.1.45
0.1.46
0.1.47
0.1.48
0.1.5
0.1.50
0.1.51
0.1.53
0.1.55
0.1.56
0.1.57
0.1.58
0.1.59
0.1.6
0.1.60
0.1.61
0.1.62
0.1.63
0.1.64
0.1.65
0.1.66
0.1.69
0.1.7
0.1.70
0.1.71
0.1.72
0.1.73
0.1.74
0.1.8
0.1.9
0.2.0
0.2.0a1
0.2.1
0.2.10
0.2.12
0.2.14
0.2.15
0.2.2
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.10
0.3.11
0.3.12
0.3.13
0.3.14
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.3.8
0.3.9
Fixed in
0.3.15
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.2.3
patch
1 CVE
CVE-2026-48776
PYSEC-2026-2575
GHSA-w39p-vh2g-g8g5
PYSEC-2026-2194
Jul 13, 2026
LangGraph SDK has unsafe URL path construction
4.2
/ 10
Medium
Network
High
Low
None
Unchanged
Low
Low
None
Summary
This issue is most consequential in deployments that:
There have no evidence of this behavior being triggered in the wild. This change is intended to reduce the surface available when caller-supplied identifier values originate from untrusted sources. Affected users / systemsYou may be affected if you:
Applications that validate identifier values (for example, by parsing them as UUIDs and rejecting anything that does not parse) before passing them to SDK methods are not affected. Validated UUIDs round-trip through the SDK request path unchanged. Impact
Patches / mitigationThe SDK now applies path-segment encoding to identifier values before they are interpolated into request URL templates. After this change, identifier values that contain characters with special meaning in URL paths are transmitted as encoded byte sequences and routed to the resource the SDK method's call site indicates. CompatibilityIdentifier values that match the standard UUID format, or any other format that contains only characters safe to transmit unencoded in URL path segments, round-trip through the SDK request path unchanged. Applications that already validate identifier inputs see no behavioral change. Operational guidance
LangSmith / hosted deployments noteThis issue affects the SDK that runs in caller applications. The LangGraph server runtime, including LangSmith-hosted deployments, receives ordinary HTTP requests on documented routes and is not itself affected by this issue. Applications that consume LangSmith-hosted services via First reported by: pucagit (CyStack). Affected versions
0.1.0
0.1.1
0.1.10
0.1.11
0.1.12
0.1.14
0.1.16
0.1.17
0.1.18
0.1.2
0.1.20
0.1.21
+ 84 more Show less
0.1.22
0.1.23
0.1.24
0.1.25
0.1.26
0.1.27
0.1.28
0.1.29
0.1.3
0.1.30
0.1.31
0.1.32
0.1.33
0.1.34
0.1.35
0.1.36
0.1.37
0.1.38
0.1.39
0.1.4
0.1.40
0.1.42
0.1.43
0.1.44
0.1.45
0.1.46
0.1.47
0.1.48
0.1.5
0.1.50
0.1.51
0.1.53
0.1.55
0.1.56
0.1.57
0.1.58
0.1.59
0.1.6
0.1.60
0.1.61
0.1.62
0.1.63
0.1.64
0.1.65
0.1.66
0.1.69
0.1.7
0.1.70
0.1.71
0.1.72
0.1.73
0.1.74
0.1.8
0.1.9
0.2.0
0.2.0a1
0.2.1
0.2.10
0.2.12
0.2.14
0.2.15
0.2.2
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.10
0.3.11
0.3.12
0.3.13
0.3.14
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.3.8
0.3.9
Fixed in
0.3.15
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.2.2
patch
1 CVE
CVE-2026-48776
PYSEC-2026-2575
GHSA-w39p-vh2g-g8g5
PYSEC-2026-2194
Jul 13, 2026
LangGraph SDK has unsafe URL path construction
4.2
/ 10
Medium
Network
High
Low
None
Unchanged
Low
Low
None
Summary
This issue is most consequential in deployments that:
There have no evidence of this behavior being triggered in the wild. This change is intended to reduce the surface available when caller-supplied identifier values originate from untrusted sources. Affected users / systemsYou may be affected if you:
Applications that validate identifier values (for example, by parsing them as UUIDs and rejecting anything that does not parse) before passing them to SDK methods are not affected. Validated UUIDs round-trip through the SDK request path unchanged. Impact
Patches / mitigationThe SDK now applies path-segment encoding to identifier values before they are interpolated into request URL templates. After this change, identifier values that contain characters with special meaning in URL paths are transmitted as encoded byte sequences and routed to the resource the SDK method's call site indicates. CompatibilityIdentifier values that match the standard UUID format, or any other format that contains only characters safe to transmit unencoded in URL path segments, round-trip through the SDK request path unchanged. Applications that already validate identifier inputs see no behavioral change. Operational guidance
LangSmith / hosted deployments noteThis issue affects the SDK that runs in caller applications. The LangGraph server runtime, including LangSmith-hosted deployments, receives ordinary HTTP requests on documented routes and is not itself affected by this issue. Applications that consume LangSmith-hosted services via First reported by: pucagit (CyStack). Affected versions
0.1.0
0.1.1
0.1.10
0.1.11
0.1.12
0.1.14
0.1.16
0.1.17
0.1.18
0.1.2
0.1.20
0.1.21
+ 84 more Show less
0.1.22
0.1.23
0.1.24
0.1.25
0.1.26
0.1.27
0.1.28
0.1.29
0.1.3
0.1.30
0.1.31
0.1.32
0.1.33
0.1.34
0.1.35
0.1.36
0.1.37
0.1.38
0.1.39
0.1.4
0.1.40
0.1.42
0.1.43
0.1.44
0.1.45
0.1.46
0.1.47
0.1.48
0.1.5
0.1.50
0.1.51
0.1.53
0.1.55
0.1.56
0.1.57
0.1.58
0.1.59
0.1.6
0.1.60
0.1.61
0.1.62
0.1.63
0.1.64
0.1.65
0.1.66
0.1.69
0.1.7
0.1.70
0.1.71
0.1.72
0.1.73
0.1.74
0.1.8
0.1.9
0.2.0
0.2.0a1
0.2.1
0.2.10
0.2.12
0.2.14
0.2.15
0.2.2
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.10
0.3.11
0.3.12
0.3.13
0.3.14
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.3.8
0.3.9
Fixed in
0.3.15
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.2.1
patch
1 CVE
CVE-2026-48776
PYSEC-2026-2575
GHSA-w39p-vh2g-g8g5
PYSEC-2026-2194
Jul 13, 2026
LangGraph SDK has unsafe URL path construction
4.2
/ 10
Medium
Network
High
Low
None
Unchanged
Low
Low
None
Summary
This issue is most consequential in deployments that:
There have no evidence of this behavior being triggered in the wild. This change is intended to reduce the surface available when caller-supplied identifier values originate from untrusted sources. Affected users / systemsYou may be affected if you:
Applications that validate identifier values (for example, by parsing them as UUIDs and rejecting anything that does not parse) before passing them to SDK methods are not affected. Validated UUIDs round-trip through the SDK request path unchanged. Impact
Patches / mitigationThe SDK now applies path-segment encoding to identifier values before they are interpolated into request URL templates. After this change, identifier values that contain characters with special meaning in URL paths are transmitted as encoded byte sequences and routed to the resource the SDK method's call site indicates. CompatibilityIdentifier values that match the standard UUID format, or any other format that contains only characters safe to transmit unencoded in URL path segments, round-trip through the SDK request path unchanged. Applications that already validate identifier inputs see no behavioral change. Operational guidance
LangSmith / hosted deployments noteThis issue affects the SDK that runs in caller applications. The LangGraph server runtime, including LangSmith-hosted deployments, receives ordinary HTTP requests on documented routes and is not itself affected by this issue. Applications that consume LangSmith-hosted services via First reported by: pucagit (CyStack). Affected versions
0.1.0
0.1.1
0.1.10
0.1.11
0.1.12
0.1.14
0.1.16
0.1.17
0.1.18
0.1.2
0.1.20
0.1.21
+ 84 more Show less
0.1.22
0.1.23
0.1.24
0.1.25
0.1.26
0.1.27
0.1.28
0.1.29
0.1.3
0.1.30
0.1.31
0.1.32
0.1.33
0.1.34
0.1.35
0.1.36
0.1.37
0.1.38
0.1.39
0.1.4
0.1.40
0.1.42
0.1.43
0.1.44
0.1.45
0.1.46
0.1.47
0.1.48
0.1.5
0.1.50
0.1.51
0.1.53
0.1.55
0.1.56
0.1.57
0.1.58
0.1.59
0.1.6
0.1.60
0.1.61
0.1.62
0.1.63
0.1.64
0.1.65
0.1.66
0.1.69
0.1.7
0.1.70
0.1.71
0.1.72
0.1.73
0.1.74
0.1.8
0.1.9
0.2.0
0.2.0a1
0.2.1
0.2.10
0.2.12
0.2.14
0.2.15
0.2.2
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.10
0.3.11
0.3.12
0.3.13
0.3.14
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.3.8
0.3.9
Fixed in
0.3.15
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.2.0
minor
1 CVE
CVE-2026-48776
PYSEC-2026-2575
GHSA-w39p-vh2g-g8g5
PYSEC-2026-2194
Jul 13, 2026
LangGraph SDK has unsafe URL path construction
4.2
/ 10
Medium
Network
High
Low
None
Unchanged
Low
Low
None
Summary
This issue is most consequential in deployments that:
There have no evidence of this behavior being triggered in the wild. This change is intended to reduce the surface available when caller-supplied identifier values originate from untrusted sources. Affected users / systemsYou may be affected if you:
Applications that validate identifier values (for example, by parsing them as UUIDs and rejecting anything that does not parse) before passing them to SDK methods are not affected. Validated UUIDs round-trip through the SDK request path unchanged. Impact
Patches / mitigationThe SDK now applies path-segment encoding to identifier values before they are interpolated into request URL templates. After this change, identifier values that contain characters with special meaning in URL paths are transmitted as encoded byte sequences and routed to the resource the SDK method's call site indicates. CompatibilityIdentifier values that match the standard UUID format, or any other format that contains only characters safe to transmit unencoded in URL path segments, round-trip through the SDK request path unchanged. Applications that already validate identifier inputs see no behavioral change. Operational guidance
LangSmith / hosted deployments noteThis issue affects the SDK that runs in caller applications. The LangGraph server runtime, including LangSmith-hosted deployments, receives ordinary HTTP requests on documented routes and is not itself affected by this issue. Applications that consume LangSmith-hosted services via First reported by: pucagit (CyStack). Affected versions
0.1.0
0.1.1
0.1.10
0.1.11
0.1.12
0.1.14
0.1.16
0.1.17
0.1.18
0.1.2
0.1.20
0.1.21
+ 84 more Show less
0.1.22
0.1.23
0.1.24
0.1.25
0.1.26
0.1.27
0.1.28
0.1.29
0.1.3
0.1.30
0.1.31
0.1.32
0.1.33
0.1.34
0.1.35
0.1.36
0.1.37
0.1.38
0.1.39
0.1.4
0.1.40
0.1.42
0.1.43
0.1.44
0.1.45
0.1.46
0.1.47
0.1.48
0.1.5
0.1.50
0.1.51
0.1.53
0.1.55
0.1.56
0.1.57
0.1.58
0.1.59
0.1.6
0.1.60
0.1.61
0.1.62
0.1.63
0.1.64
0.1.65
0.1.66
0.1.69
0.1.7
0.1.70
0.1.71
0.1.72
0.1.73
0.1.74
0.1.8
0.1.9
0.2.0
0.2.0a1
0.2.1
0.2.10
0.2.12
0.2.14
0.2.15
0.2.2
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.10
0.3.11
0.3.12
0.3.13
0.3.14
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.3.8
0.3.9
Fixed in
0.3.15
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.2.0a1
pre
1 CVE
CVE-2026-48776
PYSEC-2026-2575
GHSA-w39p-vh2g-g8g5
PYSEC-2026-2194
Jul 13, 2026
LangGraph SDK has unsafe URL path construction
4.2
/ 10
Medium
Network
High
Low
None
Unchanged
Low
Low
None
Summary
This issue is most consequential in deployments that:
There have no evidence of this behavior being triggered in the wild. This change is intended to reduce the surface available when caller-supplied identifier values originate from untrusted sources. Affected users / systemsYou may be affected if you:
Applications that validate identifier values (for example, by parsing them as UUIDs and rejecting anything that does not parse) before passing them to SDK methods are not affected. Validated UUIDs round-trip through the SDK request path unchanged. Impact
Patches / mitigationThe SDK now applies path-segment encoding to identifier values before they are interpolated into request URL templates. After this change, identifier values that contain characters with special meaning in URL paths are transmitted as encoded byte sequences and routed to the resource the SDK method's call site indicates. CompatibilityIdentifier values that match the standard UUID format, or any other format that contains only characters safe to transmit unencoded in URL path segments, round-trip through the SDK request path unchanged. Applications that already validate identifier inputs see no behavioral change. Operational guidance
LangSmith / hosted deployments noteThis issue affects the SDK that runs in caller applications. The LangGraph server runtime, including LangSmith-hosted deployments, receives ordinary HTTP requests on documented routes and is not itself affected by this issue. Applications that consume LangSmith-hosted services via First reported by: pucagit (CyStack). Affected versions
0.1.0
0.1.1
0.1.10
0.1.11
0.1.12
0.1.14
0.1.16
0.1.17
0.1.18
0.1.2
0.1.20
0.1.21
+ 84 more Show less
0.1.22
0.1.23
0.1.24
0.1.25
0.1.26
0.1.27
0.1.28
0.1.29
0.1.3
0.1.30
0.1.31
0.1.32
0.1.33
0.1.34
0.1.35
0.1.36
0.1.37
0.1.38
0.1.39
0.1.4
0.1.40
0.1.42
0.1.43
0.1.44
0.1.45
0.1.46
0.1.47
0.1.48
0.1.5
0.1.50
0.1.51
0.1.53
0.1.55
0.1.56
0.1.57
0.1.58
0.1.59
0.1.6
0.1.60
0.1.61
0.1.62
0.1.63
0.1.64
0.1.65
0.1.66
0.1.69
0.1.7
0.1.70
0.1.71
0.1.72
0.1.73
0.1.74
0.1.8
0.1.9
0.2.0
0.2.0a1
0.2.1
0.2.10
0.2.12
0.2.14
0.2.15
0.2.2
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.10
0.3.11
0.3.12
0.3.13
0.3.14
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.3.8
0.3.9
Fixed in
0.3.15
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.1.74
patch
1 CVE
CVE-2026-48776
PYSEC-2026-2575
GHSA-w39p-vh2g-g8g5
PYSEC-2026-2194
Jul 13, 2026
LangGraph SDK has unsafe URL path construction
4.2
/ 10
Medium
Network
High
Low
None
Unchanged
Low
Low
None
Summary
This issue is most consequential in deployments that:
There have no evidence of this behavior being triggered in the wild. This change is intended to reduce the surface available when caller-supplied identifier values originate from untrusted sources. Affected users / systemsYou may be affected if you:
Applications that validate identifier values (for example, by parsing them as UUIDs and rejecting anything that does not parse) before passing them to SDK methods are not affected. Validated UUIDs round-trip through the SDK request path unchanged. Impact
Patches / mitigationThe SDK now applies path-segment encoding to identifier values before they are interpolated into request URL templates. After this change, identifier values that contain characters with special meaning in URL paths are transmitted as encoded byte sequences and routed to the resource the SDK method's call site indicates. CompatibilityIdentifier values that match the standard UUID format, or any other format that contains only characters safe to transmit unencoded in URL path segments, round-trip through the SDK request path unchanged. Applications that already validate identifier inputs see no behavioral change. Operational guidance
LangSmith / hosted deployments noteThis issue affects the SDK that runs in caller applications. The LangGraph server runtime, including LangSmith-hosted deployments, receives ordinary HTTP requests on documented routes and is not itself affected by this issue. Applications that consume LangSmith-hosted services via First reported by: pucagit (CyStack). Affected versions
0.1.0
0.1.1
0.1.10
0.1.11
0.1.12
0.1.14
0.1.16
0.1.17
0.1.18
0.1.2
0.1.20
0.1.21
+ 84 more Show less
0.1.22
0.1.23
0.1.24
0.1.25
0.1.26
0.1.27
0.1.28
0.1.29
0.1.3
0.1.30
0.1.31
0.1.32
0.1.33
0.1.34
0.1.35
0.1.36
0.1.37
0.1.38
0.1.39
0.1.4
0.1.40
0.1.42
0.1.43
0.1.44
0.1.45
0.1.46
0.1.47
0.1.48
0.1.5
0.1.50
0.1.51
0.1.53
0.1.55
0.1.56
0.1.57
0.1.58
0.1.59
0.1.6
0.1.60
0.1.61
0.1.62
0.1.63
0.1.64
0.1.65
0.1.66
0.1.69
0.1.7
0.1.70
0.1.71
0.1.72
0.1.73
0.1.74
0.1.8
0.1.9
0.2.0
0.2.0a1
0.2.1
0.2.10
0.2.12
0.2.14
0.2.15
0.2.2
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.10
0.3.11
0.3.12
0.3.13
0.3.14
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.3.8
0.3.9
Fixed in
0.3.15
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.1.73
patch
1 CVE
CVE-2026-48776
PYSEC-2026-2575
GHSA-w39p-vh2g-g8g5
PYSEC-2026-2194
Jul 13, 2026
LangGraph SDK has unsafe URL path construction
4.2
/ 10
Medium
Network
High
Low
None
Unchanged
Low
Low
None
Summary
This issue is most consequential in deployments that:
There have no evidence of this behavior being triggered in the wild. This change is intended to reduce the surface available when caller-supplied identifier values originate from untrusted sources. Affected users / systemsYou may be affected if you:
Applications that validate identifier values (for example, by parsing them as UUIDs and rejecting anything that does not parse) before passing them to SDK methods are not affected. Validated UUIDs round-trip through the SDK request path unchanged. Impact
Patches / mitigationThe SDK now applies path-segment encoding to identifier values before they are interpolated into request URL templates. After this change, identifier values that contain characters with special meaning in URL paths are transmitted as encoded byte sequences and routed to the resource the SDK method's call site indicates. CompatibilityIdentifier values that match the standard UUID format, or any other format that contains only characters safe to transmit unencoded in URL path segments, round-trip through the SDK request path unchanged. Applications that already validate identifier inputs see no behavioral change. Operational guidance
LangSmith / hosted deployments noteThis issue affects the SDK that runs in caller applications. The LangGraph server runtime, including LangSmith-hosted deployments, receives ordinary HTTP requests on documented routes and is not itself affected by this issue. Applications that consume LangSmith-hosted services via First reported by: pucagit (CyStack). Affected versions
0.1.0
0.1.1
0.1.10
0.1.11
0.1.12
0.1.14
0.1.16
0.1.17
0.1.18
0.1.2
0.1.20
0.1.21
+ 84 more Show less
0.1.22
0.1.23
0.1.24
0.1.25
0.1.26
0.1.27
0.1.28
0.1.29
0.1.3
0.1.30
0.1.31
0.1.32
0.1.33
0.1.34
0.1.35
0.1.36
0.1.37
0.1.38
0.1.39
0.1.4
0.1.40
0.1.42
0.1.43
0.1.44
0.1.45
0.1.46
0.1.47
0.1.48
0.1.5
0.1.50
0.1.51
0.1.53
0.1.55
0.1.56
0.1.57
0.1.58
0.1.59
0.1.6
0.1.60
0.1.61
0.1.62
0.1.63
0.1.64
0.1.65
0.1.66
0.1.69
0.1.7
0.1.70
0.1.71
0.1.72
0.1.73
0.1.74
0.1.8
0.1.9
0.2.0
0.2.0a1
0.2.1
0.2.10
0.2.12
0.2.14
0.2.15
0.2.2
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.10
0.3.11
0.3.12
0.3.13
0.3.14
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.3.8
0.3.9
Fixed in
0.3.15
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.1.72
patch
1 CVE
CVE-2026-48776
PYSEC-2026-2575
GHSA-w39p-vh2g-g8g5
PYSEC-2026-2194
Jul 13, 2026
LangGraph SDK has unsafe URL path construction
4.2
/ 10
Medium
Network
High
Low
None
Unchanged
Low
Low
None
Summary
This issue is most consequential in deployments that:
There have no evidence of this behavior being triggered in the wild. This change is intended to reduce the surface available when caller-supplied identifier values originate from untrusted sources. Affected users / systemsYou may be affected if you:
Applications that validate identifier values (for example, by parsing them as UUIDs and rejecting anything that does not parse) before passing them to SDK methods are not affected. Validated UUIDs round-trip through the SDK request path unchanged. Impact
Patches / mitigationThe SDK now applies path-segment encoding to identifier values before they are interpolated into request URL templates. After this change, identifier values that contain characters with special meaning in URL paths are transmitted as encoded byte sequences and routed to the resource the SDK method's call site indicates. CompatibilityIdentifier values that match the standard UUID format, or any other format that contains only characters safe to transmit unencoded in URL path segments, round-trip through the SDK request path unchanged. Applications that already validate identifier inputs see no behavioral change. Operational guidance
LangSmith / hosted deployments noteThis issue affects the SDK that runs in caller applications. The LangGraph server runtime, including LangSmith-hosted deployments, receives ordinary HTTP requests on documented routes and is not itself affected by this issue. Applications that consume LangSmith-hosted services via First reported by: pucagit (CyStack). Affected versions
0.1.0
0.1.1
0.1.10
0.1.11
0.1.12
0.1.14
0.1.16
0.1.17
0.1.18
0.1.2
0.1.20
0.1.21
+ 84 more Show less
0.1.22
0.1.23
0.1.24
0.1.25
0.1.26
0.1.27
0.1.28
0.1.29
0.1.3
0.1.30
0.1.31
0.1.32
0.1.33
0.1.34
0.1.35
0.1.36
0.1.37
0.1.38
0.1.39
0.1.4
0.1.40
0.1.42
0.1.43
0.1.44
0.1.45
0.1.46
0.1.47
0.1.48
0.1.5
0.1.50
0.1.51
0.1.53
0.1.55
0.1.56
0.1.57
0.1.58
0.1.59
0.1.6
0.1.60
0.1.61
0.1.62
0.1.63
0.1.64
0.1.65
0.1.66
0.1.69
0.1.7
0.1.70
0.1.71
0.1.72
0.1.73
0.1.74
0.1.8
0.1.9
0.2.0
0.2.0a1
0.2.1
0.2.10
0.2.12
0.2.14
0.2.15
0.2.2
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.10
0.3.11
0.3.12
0.3.13
0.3.14
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.3.8
0.3.9
Fixed in
0.3.15
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.1.71
patch
1 CVE
CVE-2026-48776
PYSEC-2026-2575
GHSA-w39p-vh2g-g8g5
PYSEC-2026-2194
Jul 13, 2026
LangGraph SDK has unsafe URL path construction
4.2
/ 10
Medium
Network
High
Low
None
Unchanged
Low
Low
None
Summary
This issue is most consequential in deployments that:
There have no evidence of this behavior being triggered in the wild. This change is intended to reduce the surface available when caller-supplied identifier values originate from untrusted sources. Affected users / systemsYou may be affected if you:
Applications that validate identifier values (for example, by parsing them as UUIDs and rejecting anything that does not parse) before passing them to SDK methods are not affected. Validated UUIDs round-trip through the SDK request path unchanged. Impact
Patches / mitigationThe SDK now applies path-segment encoding to identifier values before they are interpolated into request URL templates. After this change, identifier values that contain characters with special meaning in URL paths are transmitted as encoded byte sequences and routed to the resource the SDK method's call site indicates. CompatibilityIdentifier values that match the standard UUID format, or any other format that contains only characters safe to transmit unencoded in URL path segments, round-trip through the SDK request path unchanged. Applications that already validate identifier inputs see no behavioral change. Operational guidance
LangSmith / hosted deployments noteThis issue affects the SDK that runs in caller applications. The LangGraph server runtime, including LangSmith-hosted deployments, receives ordinary HTTP requests on documented routes and is not itself affected by this issue. Applications that consume LangSmith-hosted services via First reported by: pucagit (CyStack). Affected versions
0.1.0
0.1.1
0.1.10
0.1.11
0.1.12
0.1.14
0.1.16
0.1.17
0.1.18
0.1.2
0.1.20
0.1.21
+ 84 more Show less
0.1.22
0.1.23
0.1.24
0.1.25
0.1.26
0.1.27
0.1.28
0.1.29
0.1.3
0.1.30
0.1.31
0.1.32
0.1.33
0.1.34
0.1.35
0.1.36
0.1.37
0.1.38
0.1.39
0.1.4
0.1.40
0.1.42
0.1.43
0.1.44
0.1.45
0.1.46
0.1.47
0.1.48
0.1.5
0.1.50
0.1.51
0.1.53
0.1.55
0.1.56
0.1.57
0.1.58
0.1.59
0.1.6
0.1.60
0.1.61
0.1.62
0.1.63
0.1.64
0.1.65
0.1.66
0.1.69
0.1.7
0.1.70
0.1.71
0.1.72
0.1.73
0.1.74
0.1.8
0.1.9
0.2.0
0.2.0a1
0.2.1
0.2.10
0.2.12
0.2.14
0.2.15
0.2.2
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.10
0.3.11
0.3.12
0.3.13
0.3.14
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.3.8
0.3.9
Fixed in
0.3.15
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.1.70
patch
1 CVE
CVE-2026-48776
PYSEC-2026-2575
GHSA-w39p-vh2g-g8g5
PYSEC-2026-2194
Jul 13, 2026
LangGraph SDK has unsafe URL path construction
4.2
/ 10
Medium
Network
High
Low
None
Unchanged
Low
Low
None
Summary
This issue is most consequential in deployments that:
There have no evidence of this behavior being triggered in the wild. This change is intended to reduce the surface available when caller-supplied identifier values originate from untrusted sources. Affected users / systemsYou may be affected if you:
Applications that validate identifier values (for example, by parsing them as UUIDs and rejecting anything that does not parse) before passing them to SDK methods are not affected. Validated UUIDs round-trip through the SDK request path unchanged. Impact
Patches / mitigationThe SDK now applies path-segment encoding to identifier values before they are interpolated into request URL templates. After this change, identifier values that contain characters with special meaning in URL paths are transmitted as encoded byte sequences and routed to the resource the SDK method's call site indicates. CompatibilityIdentifier values that match the standard UUID format, or any other format that contains only characters safe to transmit unencoded in URL path segments, round-trip through the SDK request path unchanged. Applications that already validate identifier inputs see no behavioral change. Operational guidance
LangSmith / hosted deployments noteThis issue affects the SDK that runs in caller applications. The LangGraph server runtime, including LangSmith-hosted deployments, receives ordinary HTTP requests on documented routes and is not itself affected by this issue. Applications that consume LangSmith-hosted services via First reported by: pucagit (CyStack). Affected versions
0.1.0
0.1.1
0.1.10
0.1.11
0.1.12
0.1.14
0.1.16
0.1.17
0.1.18
0.1.2
0.1.20
0.1.21
+ 84 more Show less
0.1.22
0.1.23
0.1.24
0.1.25
0.1.26
0.1.27
0.1.28
0.1.29
0.1.3
0.1.30
0.1.31
0.1.32
0.1.33
0.1.34
0.1.35
0.1.36
0.1.37
0.1.38
0.1.39
0.1.4
0.1.40
0.1.42
0.1.43
0.1.44
0.1.45
0.1.46
0.1.47
0.1.48
0.1.5
0.1.50
0.1.51
0.1.53
0.1.55
0.1.56
0.1.57
0.1.58
0.1.59
0.1.6
0.1.60
0.1.61
0.1.62
0.1.63
0.1.64
0.1.65
0.1.66
0.1.69
0.1.7
0.1.70
0.1.71
0.1.72
0.1.73
0.1.74
0.1.8
0.1.9
0.2.0
0.2.0a1
0.2.1
0.2.10
0.2.12
0.2.14
0.2.15
0.2.2
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.10
0.3.11
0.3.12
0.3.13
0.3.14
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.3.8
0.3.9
Fixed in
0.3.15
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.1.69
patch
1 CVE
CVE-2026-48776
PYSEC-2026-2575
GHSA-w39p-vh2g-g8g5
PYSEC-2026-2194
Jul 13, 2026
LangGraph SDK has unsafe URL path construction
4.2
/ 10
Medium
Network
High
Low
None
Unchanged
Low
Low
None
Summary
This issue is most consequential in deployments that:
There have no evidence of this behavior being triggered in the wild. This change is intended to reduce the surface available when caller-supplied identifier values originate from untrusted sources. Affected users / systemsYou may be affected if you:
Applications that validate identifier values (for example, by parsing them as UUIDs and rejecting anything that does not parse) before passing them to SDK methods are not affected. Validated UUIDs round-trip through the SDK request path unchanged. Impact
Patches / mitigationThe SDK now applies path-segment encoding to identifier values before they are interpolated into request URL templates. After this change, identifier values that contain characters with special meaning in URL paths are transmitted as encoded byte sequences and routed to the resource the SDK method's call site indicates. CompatibilityIdentifier values that match the standard UUID format, or any other format that contains only characters safe to transmit unencoded in URL path segments, round-trip through the SDK request path unchanged. Applications that already validate identifier inputs see no behavioral change. Operational guidance
LangSmith / hosted deployments noteThis issue affects the SDK that runs in caller applications. The LangGraph server runtime, including LangSmith-hosted deployments, receives ordinary HTTP requests on documented routes and is not itself affected by this issue. Applications that consume LangSmith-hosted services via First reported by: pucagit (CyStack). Affected versions
0.1.0
0.1.1
0.1.10
0.1.11
0.1.12
0.1.14
0.1.16
0.1.17
0.1.18
0.1.2
0.1.20
0.1.21
+ 84 more Show less
0.1.22
0.1.23
0.1.24
0.1.25
0.1.26
0.1.27
0.1.28
0.1.29
0.1.3
0.1.30
0.1.31
0.1.32
0.1.33
0.1.34
0.1.35
0.1.36
0.1.37
0.1.38
0.1.39
0.1.4
0.1.40
0.1.42
0.1.43
0.1.44
0.1.45
0.1.46
0.1.47
0.1.48
0.1.5
0.1.50
0.1.51
0.1.53
0.1.55
0.1.56
0.1.57
0.1.58
0.1.59
0.1.6
0.1.60
0.1.61
0.1.62
0.1.63
0.1.64
0.1.65
0.1.66
0.1.69
0.1.7
0.1.70
0.1.71
0.1.72
0.1.73
0.1.74
0.1.8
0.1.9
0.2.0
0.2.0a1
0.2.1
0.2.10
0.2.12
0.2.14
0.2.15
0.2.2
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.10
0.3.11
0.3.12
0.3.13
0.3.14
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.3.8
0.3.9
Fixed in
0.3.15
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.1.66
patch
1 CVE
CVE-2026-48776
PYSEC-2026-2575
GHSA-w39p-vh2g-g8g5
PYSEC-2026-2194
Jul 13, 2026
LangGraph SDK has unsafe URL path construction
4.2
/ 10
Medium
Network
High
Low
None
Unchanged
Low
Low
None
Summary
This issue is most consequential in deployments that:
There have no evidence of this behavior being triggered in the wild. This change is intended to reduce the surface available when caller-supplied identifier values originate from untrusted sources. Affected users / systemsYou may be affected if you:
Applications that validate identifier values (for example, by parsing them as UUIDs and rejecting anything that does not parse) before passing them to SDK methods are not affected. Validated UUIDs round-trip through the SDK request path unchanged. Impact
Patches / mitigationThe SDK now applies path-segment encoding to identifier values before they are interpolated into request URL templates. After this change, identifier values that contain characters with special meaning in URL paths are transmitted as encoded byte sequences and routed to the resource the SDK method's call site indicates. CompatibilityIdentifier values that match the standard UUID format, or any other format that contains only characters safe to transmit unencoded in URL path segments, round-trip through the SDK request path unchanged. Applications that already validate identifier inputs see no behavioral change. Operational guidance
LangSmith / hosted deployments noteThis issue affects the SDK that runs in caller applications. The LangGraph server runtime, including LangSmith-hosted deployments, receives ordinary HTTP requests on documented routes and is not itself affected by this issue. Applications that consume LangSmith-hosted services via First reported by: pucagit (CyStack). Affected versions
0.1.0
0.1.1
0.1.10
0.1.11
0.1.12
0.1.14
0.1.16
0.1.17
0.1.18
0.1.2
0.1.20
0.1.21
+ 84 more Show less
0.1.22
0.1.23
0.1.24
0.1.25
0.1.26
0.1.27
0.1.28
0.1.29
0.1.3
0.1.30
0.1.31
0.1.32
0.1.33
0.1.34
0.1.35
0.1.36
0.1.37
0.1.38
0.1.39
0.1.4
0.1.40
0.1.42
0.1.43
0.1.44
0.1.45
0.1.46
0.1.47
0.1.48
0.1.5
0.1.50
0.1.51
0.1.53
0.1.55
0.1.56
0.1.57
0.1.58
0.1.59
0.1.6
0.1.60
0.1.61
0.1.62
0.1.63
0.1.64
0.1.65
0.1.66
0.1.69
0.1.7
0.1.70
0.1.71
0.1.72
0.1.73
0.1.74
0.1.8
0.1.9
0.2.0
0.2.0a1
0.2.1
0.2.10
0.2.12
0.2.14
0.2.15
0.2.2
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.10
0.3.11
0.3.12
0.3.13
0.3.14
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.3.8
0.3.9
Fixed in
0.3.15
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.1.65
patch
1 CVE
CVE-2026-48776
PYSEC-2026-2575
GHSA-w39p-vh2g-g8g5
PYSEC-2026-2194
Jul 13, 2026
LangGraph SDK has unsafe URL path construction
4.2
/ 10
Medium
Network
High
Low
None
Unchanged
Low
Low
None
Summary
This issue is most consequential in deployments that:
There have no evidence of this behavior being triggered in the wild. This change is intended to reduce the surface available when caller-supplied identifier values originate from untrusted sources. Affected users / systemsYou may be affected if you:
Applications that validate identifier values (for example, by parsing them as UUIDs and rejecting anything that does not parse) before passing them to SDK methods are not affected. Validated UUIDs round-trip through the SDK request path unchanged. Impact
Patches / mitigationThe SDK now applies path-segment encoding to identifier values before they are interpolated into request URL templates. After this change, identifier values that contain characters with special meaning in URL paths are transmitted as encoded byte sequences and routed to the resource the SDK method's call site indicates. CompatibilityIdentifier values that match the standard UUID format, or any other format that contains only characters safe to transmit unencoded in URL path segments, round-trip through the SDK request path unchanged. Applications that already validate identifier inputs see no behavioral change. Operational guidance
LangSmith / hosted deployments noteThis issue affects the SDK that runs in caller applications. The LangGraph server runtime, including LangSmith-hosted deployments, receives ordinary HTTP requests on documented routes and is not itself affected by this issue. Applications that consume LangSmith-hosted services via First reported by: pucagit (CyStack). Affected versions
0.1.0
0.1.1
0.1.10
0.1.11
0.1.12
0.1.14
0.1.16
0.1.17
0.1.18
0.1.2
0.1.20
0.1.21
+ 84 more Show less
0.1.22
0.1.23
0.1.24
0.1.25
0.1.26
0.1.27
0.1.28
0.1.29
0.1.3
0.1.30
0.1.31
0.1.32
0.1.33
0.1.34
0.1.35
0.1.36
0.1.37
0.1.38
0.1.39
0.1.4
0.1.40
0.1.42
0.1.43
0.1.44
0.1.45
0.1.46
0.1.47
0.1.48
0.1.5
0.1.50
0.1.51
0.1.53
0.1.55
0.1.56
0.1.57
0.1.58
0.1.59
0.1.6
0.1.60
0.1.61
0.1.62
0.1.63
0.1.64
0.1.65
0.1.66
0.1.69
0.1.7
0.1.70
0.1.71
0.1.72
0.1.73
0.1.74
0.1.8
0.1.9
0.2.0
0.2.0a1
0.2.1
0.2.10
0.2.12
0.2.14
0.2.15
0.2.2
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.10
0.3.11
0.3.12
0.3.13
0.3.14
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.3.8
0.3.9
Fixed in
0.3.15
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.1.64
patch
1 CVE
CVE-2026-48776
PYSEC-2026-2575
GHSA-w39p-vh2g-g8g5
PYSEC-2026-2194
Jul 13, 2026
LangGraph SDK has unsafe URL path construction
4.2
/ 10
Medium
Network
High
Low
None
Unchanged
Low
Low
None
Summary
This issue is most consequential in deployments that:
There have no evidence of this behavior being triggered in the wild. This change is intended to reduce the surface available when caller-supplied identifier values originate from untrusted sources. Affected users / systemsYou may be affected if you:
Applications that validate identifier values (for example, by parsing them as UUIDs and rejecting anything that does not parse) before passing them to SDK methods are not affected. Validated UUIDs round-trip through the SDK request path unchanged. Impact
Patches / mitigationThe SDK now applies path-segment encoding to identifier values before they are interpolated into request URL templates. After this change, identifier values that contain characters with special meaning in URL paths are transmitted as encoded byte sequences and routed to the resource the SDK method's call site indicates. CompatibilityIdentifier values that match the standard UUID format, or any other format that contains only characters safe to transmit unencoded in URL path segments, round-trip through the SDK request path unchanged. Applications that already validate identifier inputs see no behavioral change. Operational guidance
LangSmith / hosted deployments noteThis issue affects the SDK that runs in caller applications. The LangGraph server runtime, including LangSmith-hosted deployments, receives ordinary HTTP requests on documented routes and is not itself affected by this issue. Applications that consume LangSmith-hosted services via First reported by: pucagit (CyStack). Affected versions
0.1.0
0.1.1
0.1.10
0.1.11
0.1.12
0.1.14
0.1.16
0.1.17
0.1.18
0.1.2
0.1.20
0.1.21
+ 84 more Show less
0.1.22
0.1.23
0.1.24
0.1.25
0.1.26
0.1.27
0.1.28
0.1.29
0.1.3
0.1.30
0.1.31
0.1.32
0.1.33
0.1.34
0.1.35
0.1.36
0.1.37
0.1.38
0.1.39
0.1.4
0.1.40
0.1.42
0.1.43
0.1.44
0.1.45
0.1.46
0.1.47
0.1.48
0.1.5
0.1.50
0.1.51
0.1.53
0.1.55
0.1.56
0.1.57
0.1.58
0.1.59
0.1.6
0.1.60
0.1.61
0.1.62
0.1.63
0.1.64
0.1.65
0.1.66
0.1.69
0.1.7
0.1.70
0.1.71
0.1.72
0.1.73
0.1.74
0.1.8
0.1.9
0.2.0
0.2.0a1
0.2.1
0.2.10
0.2.12
0.2.14
0.2.15
0.2.2
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.10
0.3.11
0.3.12
0.3.13
0.3.14
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.3.8
0.3.9
Fixed in
0.3.15
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.1.63
patch
1 CVE
CVE-2026-48776
PYSEC-2026-2575
GHSA-w39p-vh2g-g8g5
PYSEC-2026-2194
Jul 13, 2026
LangGraph SDK has unsafe URL path construction
4.2
/ 10
Medium
Network
High
Low
None
Unchanged
Low
Low
None
Summary
This issue is most consequential in deployments that:
There have no evidence of this behavior being triggered in the wild. This change is intended to reduce the surface available when caller-supplied identifier values originate from untrusted sources. Affected users / systemsYou may be affected if you:
Applications that validate identifier values (for example, by parsing them as UUIDs and rejecting anything that does not parse) before passing them to SDK methods are not affected. Validated UUIDs round-trip through the SDK request path unchanged. Impact
Patches / mitigationThe SDK now applies path-segment encoding to identifier values before they are interpolated into request URL templates. After this change, identifier values that contain characters with special meaning in URL paths are transmitted as encoded byte sequences and routed to the resource the SDK method's call site indicates. CompatibilityIdentifier values that match the standard UUID format, or any other format that contains only characters safe to transmit unencoded in URL path segments, round-trip through the SDK request path unchanged. Applications that already validate identifier inputs see no behavioral change. Operational guidance
LangSmith / hosted deployments noteThis issue affects the SDK that runs in caller applications. The LangGraph server runtime, including LangSmith-hosted deployments, receives ordinary HTTP requests on documented routes and is not itself affected by this issue. Applications that consume LangSmith-hosted services via First reported by: pucagit (CyStack). Affected versions
0.1.0
0.1.1
0.1.10
0.1.11
0.1.12
0.1.14
0.1.16
0.1.17
0.1.18
0.1.2
0.1.20
0.1.21
+ 84 more Show less
0.1.22
0.1.23
0.1.24
0.1.25
0.1.26
0.1.27
0.1.28
0.1.29
0.1.3
0.1.30
0.1.31
0.1.32
0.1.33
0.1.34
0.1.35
0.1.36
0.1.37
0.1.38
0.1.39
0.1.4
0.1.40
0.1.42
0.1.43
0.1.44
0.1.45
0.1.46
0.1.47
0.1.48
0.1.5
0.1.50
0.1.51
0.1.53
0.1.55
0.1.56
0.1.57
0.1.58
0.1.59
0.1.6
0.1.60
0.1.61
0.1.62
0.1.63
0.1.64
0.1.65
0.1.66
0.1.69
0.1.7
0.1.70
0.1.71
0.1.72
0.1.73
0.1.74
0.1.8
0.1.9
0.2.0
0.2.0a1
0.2.1
0.2.10
0.2.12
0.2.14
0.2.15
0.2.2
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.10
0.3.11
0.3.12
0.3.13
0.3.14
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.3.8
0.3.9
Fixed in
0.3.15
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.1.62
patch
1 CVE
CVE-2026-48776
PYSEC-2026-2575
GHSA-w39p-vh2g-g8g5
PYSEC-2026-2194
Jul 13, 2026
LangGraph SDK has unsafe URL path construction
4.2
/ 10
Medium
Network
High
Low
None
Unchanged
Low
Low
None
Summary
This issue is most consequential in deployments that:
There have no evidence of this behavior being triggered in the wild. This change is intended to reduce the surface available when caller-supplied identifier values originate from untrusted sources. Affected users / systemsYou may be affected if you:
Applications that validate identifier values (for example, by parsing them as UUIDs and rejecting anything that does not parse) before passing them to SDK methods are not affected. Validated UUIDs round-trip through the SDK request path unchanged. Impact
Patches / mitigationThe SDK now applies path-segment encoding to identifier values before they are interpolated into request URL templates. After this change, identifier values that contain characters with special meaning in URL paths are transmitted as encoded byte sequences and routed to the resource the SDK method's call site indicates. CompatibilityIdentifier values that match the standard UUID format, or any other format that contains only characters safe to transmit unencoded in URL path segments, round-trip through the SDK request path unchanged. Applications that already validate identifier inputs see no behavioral change. Operational guidance
LangSmith / hosted deployments noteThis issue affects the SDK that runs in caller applications. The LangGraph server runtime, including LangSmith-hosted deployments, receives ordinary HTTP requests on documented routes and is not itself affected by this issue. Applications that consume LangSmith-hosted services via First reported by: pucagit (CyStack). Affected versions
0.1.0
0.1.1
0.1.10
0.1.11
0.1.12
0.1.14
0.1.16
0.1.17
0.1.18
0.1.2
0.1.20
0.1.21
+ 84 more Show less
0.1.22
0.1.23
0.1.24
0.1.25
0.1.26
0.1.27
0.1.28
0.1.29
0.1.3
0.1.30
0.1.31
0.1.32
0.1.33
0.1.34
0.1.35
0.1.36
0.1.37
0.1.38
0.1.39
0.1.4
0.1.40
0.1.42
0.1.43
0.1.44
0.1.45
0.1.46
0.1.47
0.1.48
0.1.5
0.1.50
0.1.51
0.1.53
0.1.55
0.1.56
0.1.57
0.1.58
0.1.59
0.1.6
0.1.60
0.1.61
0.1.62
0.1.63
0.1.64
0.1.65
0.1.66
0.1.69
0.1.7
0.1.70
0.1.71
0.1.72
0.1.73
0.1.74
0.1.8
0.1.9
0.2.0
0.2.0a1
0.2.1
0.2.10
0.2.12
0.2.14
0.2.15
0.2.2
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.10
0.3.11
0.3.12
0.3.13
0.3.14
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.3.8
0.3.9
Fixed in
0.3.15
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.1.61
patch
1 CVE
CVE-2026-48776
PYSEC-2026-2575
GHSA-w39p-vh2g-g8g5
PYSEC-2026-2194
Jul 13, 2026
LangGraph SDK has unsafe URL path construction
4.2
/ 10
Medium
Network
High
Low
None
Unchanged
Low
Low
None
Summary
This issue is most consequential in deployments that:
There have no evidence of this behavior being triggered in the wild. This change is intended to reduce the surface available when caller-supplied identifier values originate from untrusted sources. Affected users / systemsYou may be affected if you:
Applications that validate identifier values (for example, by parsing them as UUIDs and rejecting anything that does not parse) before passing them to SDK methods are not affected. Validated UUIDs round-trip through the SDK request path unchanged. Impact
Patches / mitigationThe SDK now applies path-segment encoding to identifier values before they are interpolated into request URL templates. After this change, identifier values that contain characters with special meaning in URL paths are transmitted as encoded byte sequences and routed to the resource the SDK method's call site indicates. CompatibilityIdentifier values that match the standard UUID format, or any other format that contains only characters safe to transmit unencoded in URL path segments, round-trip through the SDK request path unchanged. Applications that already validate identifier inputs see no behavioral change. Operational guidance
LangSmith / hosted deployments noteThis issue affects the SDK that runs in caller applications. The LangGraph server runtime, including LangSmith-hosted deployments, receives ordinary HTTP requests on documented routes and is not itself affected by this issue. Applications that consume LangSmith-hosted services via First reported by: pucagit (CyStack). Affected versions
0.1.0
0.1.1
0.1.10
0.1.11
0.1.12
0.1.14
0.1.16
0.1.17
0.1.18
0.1.2
0.1.20
0.1.21
+ 84 more Show less
0.1.22
0.1.23
0.1.24
0.1.25
0.1.26
0.1.27
0.1.28
0.1.29
0.1.3
0.1.30
0.1.31
0.1.32
0.1.33
0.1.34
0.1.35
0.1.36
0.1.37
0.1.38
0.1.39
0.1.4
0.1.40
0.1.42
0.1.43
0.1.44
0.1.45
0.1.46
0.1.47
0.1.48
0.1.5
0.1.50
0.1.51
0.1.53
0.1.55
0.1.56
0.1.57
0.1.58
0.1.59
0.1.6
0.1.60
0.1.61
0.1.62
0.1.63
0.1.64
0.1.65
0.1.66
0.1.69
0.1.7
0.1.70
0.1.71
0.1.72
0.1.73
0.1.74
0.1.8
0.1.9
0.2.0
0.2.0a1
0.2.1
0.2.10
0.2.12
0.2.14
0.2.15
0.2.2
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.10
0.3.11
0.3.12
0.3.13
0.3.14
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.3.8
0.3.9
Fixed in
0.3.15
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.1.60
patch
1 CVE
CVE-2026-48776
PYSEC-2026-2575
GHSA-w39p-vh2g-g8g5
PYSEC-2026-2194
Jul 13, 2026
LangGraph SDK has unsafe URL path construction
4.2
/ 10
Medium
Network
High
Low
None
Unchanged
Low
Low
None
Summary
This issue is most consequential in deployments that:
There have no evidence of this behavior being triggered in the wild. This change is intended to reduce the surface available when caller-supplied identifier values originate from untrusted sources. Affected users / systemsYou may be affected if you:
Applications that validate identifier values (for example, by parsing them as UUIDs and rejecting anything that does not parse) before passing them to SDK methods are not affected. Validated UUIDs round-trip through the SDK request path unchanged. Impact
Patches / mitigationThe SDK now applies path-segment encoding to identifier values before they are interpolated into request URL templates. After this change, identifier values that contain characters with special meaning in URL paths are transmitted as encoded byte sequences and routed to the resource the SDK method's call site indicates. CompatibilityIdentifier values that match the standard UUID format, or any other format that contains only characters safe to transmit unencoded in URL path segments, round-trip through the SDK request path unchanged. Applications that already validate identifier inputs see no behavioral change. Operational guidance
LangSmith / hosted deployments noteThis issue affects the SDK that runs in caller applications. The LangGraph server runtime, including LangSmith-hosted deployments, receives ordinary HTTP requests on documented routes and is not itself affected by this issue. Applications that consume LangSmith-hosted services via First reported by: pucagit (CyStack). Affected versions
0.1.0
0.1.1
0.1.10
0.1.11
0.1.12
0.1.14
0.1.16
0.1.17
0.1.18
0.1.2
0.1.20
0.1.21
+ 84 more Show less
0.1.22
0.1.23
0.1.24
0.1.25
0.1.26
0.1.27
0.1.28
0.1.29
0.1.3
0.1.30
0.1.31
0.1.32
0.1.33
0.1.34
0.1.35
0.1.36
0.1.37
0.1.38
0.1.39
0.1.4
0.1.40
0.1.42
0.1.43
0.1.44
0.1.45
0.1.46
0.1.47
0.1.48
0.1.5
0.1.50
0.1.51
0.1.53
0.1.55
0.1.56
0.1.57
0.1.58
0.1.59
0.1.6
0.1.60
0.1.61
0.1.62
0.1.63
0.1.64
0.1.65
0.1.66
0.1.69
0.1.7
0.1.70
0.1.71
0.1.72
0.1.73
0.1.74
0.1.8
0.1.9
0.2.0
0.2.0a1
0.2.1
0.2.10
0.2.12
0.2.14
0.2.15
0.2.2
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.10
0.3.11
0.3.12
0.3.13
0.3.14
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.3.8
0.3.9
Fixed in
0.3.15
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.1.59
patch
1 CVE
CVE-2026-48776
PYSEC-2026-2575
GHSA-w39p-vh2g-g8g5
PYSEC-2026-2194
Jul 13, 2026
LangGraph SDK has unsafe URL path construction
4.2
/ 10
Medium
Network
High
Low
None
Unchanged
Low
Low
None
Summary
This issue is most consequential in deployments that:
There have no evidence of this behavior being triggered in the wild. This change is intended to reduce the surface available when caller-supplied identifier values originate from untrusted sources. Affected users / systemsYou may be affected if you:
Applications that validate identifier values (for example, by parsing them as UUIDs and rejecting anything that does not parse) before passing them to SDK methods are not affected. Validated UUIDs round-trip through the SDK request path unchanged. Impact
Patches / mitigationThe SDK now applies path-segment encoding to identifier values before they are interpolated into request URL templates. After this change, identifier values that contain characters with special meaning in URL paths are transmitted as encoded byte sequences and routed to the resource the SDK method's call site indicates. CompatibilityIdentifier values that match the standard UUID format, or any other format that contains only characters safe to transmit unencoded in URL path segments, round-trip through the SDK request path unchanged. Applications that already validate identifier inputs see no behavioral change. Operational guidance
LangSmith / hosted deployments noteThis issue affects the SDK that runs in caller applications. The LangGraph server runtime, including LangSmith-hosted deployments, receives ordinary HTTP requests on documented routes and is not itself affected by this issue. Applications that consume LangSmith-hosted services via First reported by: pucagit (CyStack). Affected versions
0.1.0
0.1.1
0.1.10
0.1.11
0.1.12
0.1.14
0.1.16
0.1.17
0.1.18
0.1.2
0.1.20
0.1.21
+ 84 more Show less
0.1.22
0.1.23
0.1.24
0.1.25
0.1.26
0.1.27
0.1.28
0.1.29
0.1.3
0.1.30
0.1.31
0.1.32
0.1.33
0.1.34
0.1.35
0.1.36
0.1.37
0.1.38
0.1.39
0.1.4
0.1.40
0.1.42
0.1.43
0.1.44
0.1.45
0.1.46
0.1.47
0.1.48
0.1.5
0.1.50
0.1.51
0.1.53
0.1.55
0.1.56
0.1.57
0.1.58
0.1.59
0.1.6
0.1.60
0.1.61
0.1.62
0.1.63
0.1.64
0.1.65
0.1.66
0.1.69
0.1.7
0.1.70
0.1.71
0.1.72
0.1.73
0.1.74
0.1.8
0.1.9
0.2.0
0.2.0a1
0.2.1
0.2.10
0.2.12
0.2.14
0.2.15
0.2.2
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.10
0.3.11
0.3.12
0.3.13
0.3.14
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.3.8
0.3.9
Fixed in
0.3.15
References
Updated Jul 13, 2026 · Source: OSV.dev |