#10683·livewire

enum property in component with malformed POST causes wrongful error 500

Author: afracaCreated Sep 8, 2026Updated Sep 12, 2026

Livewire version

4.3.3

Laravel version

13.21.1

PHP version

8.5.8

Browser and operating system

Firefox on MacOS

Describe the issue you're experiencing

A component with a backed-enum typed property throws an unhandled TypeError (HTTP 500, reported to Sentry as an application bug) whenever the updates map in an update request carries a non-scalar value for that property.

TypeError: App\Enums\AuthIndexForm::from(): Argument #1 ($value) must be of type int, array given
  at vendor/livewire/livewire/src/Mechanisms/HandleComponents/Synthesizers/EnumSynth.php:34

Code snippets to reproduce the issue

php
enum Status: int
{
    case Draft = 0;
    case Published = 1;
}

class Post extends Component
{
    public Status $status = Status::Draft;

    public function render()
    {
        return '<div></div>';
    }
}
php
Livewire::test(Post::class)->set('status', []); // TypeError, 500

Screenshots/screen recordings

No response

How do you expect it to work?

Livewire already recognises and handles this exact class of traffic. HandleComponents::setComponentPropertyAwareOfTypes() (line 647) reads:

php
// This is almost certainly a bot/scanner probing typed properties
// with wrong-type values. Abort with 419 directly so it never
// reaches the top-level catch (which would report it as a real bug).
if (config('app.debug')) throw $e;

abort(419);

Please confirm (incomplete submissions will not be addressed)

  • I have provided easy and step-by-step instructions to reproduce the bug.
  • I have provided code samples as text and NOT images.
  • I understand my bug report will be removed if I haven't met the criteria above.