Well, a one man company probably shouldn't be a maintainer on something unless it is critical to their business. As he discovered, the model is that big rich companies pay someone to maintain the stuff that they need. Customers like it open source. Multiple companies maintaining the same stuff makes it easier to ensure that everyone that needs the product gets to keep using it and reduces the cost.
Personally, I don't really like products where one overworked guy is the maintainer. It sounds fragile to me. That is why I never used putty, for example. And wouldn't incorporate it into things at work. And, if you found a bug in a library, you are probably a developer. It's open source, submit a patch with your security bug.
I agree with the author, if it isn't a high priority/critical security bug, its just a bug and can be picked up in the normal release schedule. I'm not even really sure what a security bug is that isn't high priority, but that is another matter.