ClutchPoints
Brendan Sorsby has been one of the most talked-about individuals due to his alleged gambling scandal during his college football career. With the would-be redshirt senior no longer playing next season, he is set to enter the NFL Supplemental Draft soon. With speculation growing about which teams might be interested, the rumor mill pegs the Pittsburgh Steelers as a potential home for Sorsby.
During a guest appearance on “The Yinziders,” Mike DeFabo of The Athletic claimed that the Steelers are at least considering and gauging their options with Sorsby. DeFabo claims the gambling scandal is not something the organization is concerned with.
“It sounds like right now, the Steelers are currently doing their homework,” said DeFabo about Sorsby. “It sounds like [the gambling issue] at this point would not be a disqualifier for the Steelers.”
Several NFL insiders value Brendan Sorsby as a second-round pick, with some believing he would have been the second-best quarterback prospect in the 2026 NFL Draft behind Fernando Mendoza.
For the Steelers, the club already has a somewhat crowded quarterback room. Aaron Rodgers is the starter, and it is believed this will be his final season in the league. Pittsburgh also has veteran backup Mason Rudolph, 2o25 sixth-round pick Will Howard, and 2026 third-round pick Drew Allar.
If the rumors are true and the Steelers acquire Sorsby through the Supplemental Draft, then whatever pick the front office uses to select him with, the franchise loses that pick for the 2027 NFL Draft. So, there is a risk involved for any team considering Sorsby.
Brendan Sorsby played four years of college football, two with the Indiana Hoosiers and two with the Cincinnati Bearcats. He is considered a dual-threat quarterback, as he ended last season with 2,800 passing yards, 580 rushing yards (career-best), and 36 total touchdowns (27 passing, 9 rushing) while completing 61.6% of his pass attempts.
The post Steelers rumors: Brendan Sorsby selection on table despite gambling scandal appeared first on ClutchPoints.
