{"items":[{"id":"NVI-00004212","kind":"vulnerability","title":"Laravel Guard bypass in Eloquent models","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-44pg-c29v-hp6r"],"plain_summary":"OSV carries this publisher advisory for laravel/framework, laravel/framework, laravel/framework. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 6.18.34 for laravel/framework. Confirm the publisher’s latest guidance.","source_ids":["sr-5d2ff7214fc7e1d527ad6d56ad80a01b"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 7.23.2 for laravel/framework. Confirm the publisher’s latest guidance.","source_ids":["sr-5d2ff7214fc7e1d527ad6d56ad80a01b"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-5d2ff7214fc7e1d527ad6d56ad80a01b","url":"https://github.com/advisories/GHSA-44pg-c29v-hp6r","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-44pg-c29v-hp6r","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:49.664Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-5d2ff7214fc7e1d527ad6d56ad80a01b"],"technology":"laravel/framework","known_exclusions":[],"conditions_summary":"In laravel releases before 6.18.34 and 7.23.2. It was possible to mass assign Eloquent attributes that included the model's table name:\n```\n$model->fill(['users.name' => 'Taylor']);\n```\nWhen doing so, Eloquent would remove the table name from the attribute for you. This was a \"convenience\" feature of Eloquent and was not documented.\n\nHowever, when paired with validation, this can lead to unexpected and unvalidated values being saved to the database. For this reason, we have removed the automatic stripping of table names from mass-asignment operations so that the attributes go through the typical \"fillable\" / \"guarded\" logic. Any attributes containing table names that are not explicitly declared as fillable will be discarded.\n\nThis security release will be a breaking change for applications that were relying on the undocumented table name stripping during mass assignment. Since this feature was relatively unknown and undocumented, we expect the vast majority of Laravel applications to be able to upgrade without issues.","public_affected_ranges":["ECOSYSTEM: introduced 5.5.0; last_affected 5.5.49"]},{"certainty":"source_listed","source_ids":["sr-5d2ff7214fc7e1d527ad6d56ad80a01b"],"technology":"laravel/framework","known_exclusions":[],"conditions_summary":"In laravel releases before 6.18.34 and 7.23.2. It was possible to mass assign Eloquent attributes that included the model's table name:\n```\n$model->fill(['users.name' => 'Taylor']);\n```\nWhen doing so, Eloquent would remove the table name from the attribute for you. This was a \"convenience\" feature of Eloquent and was not documented.\n\nHowever, when paired with validation, this can lead to unexpected and unvalidated values being saved to the database. For this reason, we have removed the automatic stripping of table names from mass-asignment operations so that the attributes go through the typical \"fillable\" / \"guarded\" logic. Any attributes containing table names that are not explicitly declared as fillable will be discarded.\n\nThis security release will be a breaking change for applications that were relying on the undocumented table name stripping during mass assignment. Since this feature was relatively unknown and undocumented, we expect the vast majority of Laravel applications to be able to upgrade without issues.","public_affected_ranges":["ECOSYSTEM: introduced 6.0.0; fixed 6.18.34"]},{"certainty":"source_listed","source_ids":["sr-5d2ff7214fc7e1d527ad6d56ad80a01b"],"technology":"laravel/framework","known_exclusions":[],"conditions_summary":"In laravel releases before 6.18.34 and 7.23.2. It was possible to mass assign Eloquent attributes that included the model's table name:\n```\n$model->fill(['users.name' => 'Taylor']);\n```\nWhen doing so, Eloquent would remove the table name from the attribute for you. This was a \"convenience\" feature of Eloquent and was not documented.\n\nHowever, when paired with validation, this can lead to unexpected and unvalidated values being saved to the database. For this reason, we have removed the automatic stripping of table names from mass-asignment operations so that the attributes go through the typical \"fillable\" / \"guarded\" logic. Any attributes containing table names that are not explicitly declared as fillable will be discarded.\n\nThis security release will be a breaking change for applications that were relying on the undocumented table name stripping during mass assignment. Since this feature was relatively unknown and undocumented, we expect the vast majority of Laravel applications to be able to upgrade without issues.","public_affected_ranges":["ECOSYSTEM: introduced 7.0.0; fixed 7.23.2"]}],"null_published_at":"2026-10-31T22:12:52.634Z","source_updated_at":"2024-11-29T05:40:49.412Z","source_disclosed_at":"2024-05-15T22:18:33.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-10-31T21:41:49.664Z"}],"next_cursor":null,"snapshot_revision":"42594"}