@Junaid32092262a1i8, you haven't said what CF version you're on. Assuming it's cf2018 or above, some good news is that DOES have null support--though it must be enabled. It is not, by default (so you'd get that error until you do enable it).
You can enable it in the cf admin (first settings page), or in your application (either this.enablenullsupport=yes in application.cfc or as an attribute of cfapplication in application.cfm).
The feature (and setting it) is described in the docs:
https://helpx.adobe.com/coldfusion/developing-applications/the-cfml-programming-language/using-coldfusion-variables/data-types-developing-guide.html#null-support
And also in an Adobe blog post from 2018 (which has some quirks)
https://coldfusion.adobe.com/2018/07/null-support-in-coldfusion-2018
Neither makes clear that you also must cause cf to recompile the program using the null, for this change of behavior to take effect. You can cause that simply by editing the file i(n any way: add and remove a space, for instance), then save it and re-run the request.
(Technically the docs mention it, but elsewhere on that page, about how changes affecting datatype are indeed at compile time--which can be changed via a JVM arg at cf startup.)
Let us know how it goes.