13.2.0 - 2026-11-19
This release contains a security fix. Upgrading is recommended for all applications that use interactive server rendering.
Improvements
- ExpressionParser gets
ExpressionParser.AllowMethodandExpressionParser.AllowType. Call them when the application starts to let filter, sort and select expression strings call your own methods, for exampleExpressionParser.AllowType(typeof(MyApp.Filters.Helpers)). - Form components expose
aria-invalid="true"on the element that carries the role when the field has validation messages in theEditContext. A consumer's ownaria-invalidis kept.
Fixes
- ExpressionParser checks every parsed expression against an allow list. Methods and operators are limited to framework value types,
Math,Convertand LINQ operators, and access to reflection types and to static members of other types is rejected. An expression string that calls an application method now throws anInvalidOperationExceptionwhose message shows theAllowMethodorAllowTypecall to add.PadLeft,PadRight,InternandIsInternedare not allowed on strings. - ExpressionParser and property paths used for sorting, grouping and column values read public members only. A column bound to an internal or private property needs that property to be public.
- ExpressionParser rejects expressions that are too large or too deeply nested with an
InvalidOperationExceptioninstead of ending the process. A single filter is limited to about 285 conditions, and a property path to 10 segments. - ExpressionParser no longer throws
IndexOutOfRangeExceptionfor a LINQ method on a non-generic sequence, and anonymous projections with the same shape reuse one generated type. - ExpressionSerializer writes string and character values that contain a backslash so that they read back as the same value. The filter string in
LoadDataArgs.Filterwas not escaped fully for such values. - DataGrid
LoadSettingskeeps a restored group only when it refers to a public property of the item. Saved settings are user input: keep them on the server when the grid is bound to objects with data the user is not allowed to see. - Numeric keeps an
aria-invalidsupplied throughInputAttributes. It was rendered after the attribute splat and removed the consumer's value (#2833).