I can confirm this issue with the setup below.

The issue was introduced in rBae4407034114: Cycles: explicitly skip self-intersection. CC @Brecht Van Lommel (brecht)

System Information
Operating system: Linux-5.16.0-3-amd64-x86_64-with-glibc2.33 64 Bits
Graphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.54
Blender version: 3.2.0 Alpha, branch: master, commit date: 2022-03-17 16:52, hash: rB7fed4c06c2ff

idk if related but in some test renders I did recently with like 256 bounces or something I thought it looked overly bright for having shaders that shouldn't be emitting more then possible I had one that wasn't even fixing that it looked to bright to me. If I can reproduce it I'll post it most likely I have another report in the works though so might take a few days. But I'm really not getting why there being a .blend that test just about every thing like this in one go hasn't been some we have for each blender release that would fix things like this from getting missed in optimizations.

In T96576#1327321, @Connor M. Denning (ConMan) wrote:

idk if related but in some test renders I did recently with like 256 bounces or something I thought it looked overly bright for having shaders that shouldn't be emitting more then possible I had one that wasn't even fixing that it looked to bright to me. If I can reproduce it I'll post it most likely I have another report in the works though so might take a few days. But I'm really not getting why there being a .blend that test just about every thing like this in one go hasn't been some we have for each blender release that would fix things like this from getting missed in optimizations.

There was a issue reported recently of the Principled BSDF reflecting more light than it theoretically should in the specular part of the material when the material base colour was above a certain threshold. This might of been what you were experiencing? If so, it has already been reported and it is not considered a "bug". Apparently this is because the Principled BSDF is based on a shader from a white paper from Disney. And the shader proposed by Disney has this exact same issue. Cycles replicates this issue to ensure compatibility between other software using the same shader model (which also most likely have that issue).

In T96576#1327386, @Alaska (Alaska) wrote:

In T96576#1327321, @Connor M. Denning (ConMan) wrote:

idk if related but in some test renders I did recently with like 256 bounces or something I thought it looked overly bright for having shaders that shouldn't be emitting more then possible I had one that wasn't even fixing that it looked to bright to me. If I can reproduce it I'll post it most likely I have another report in the works though so might take a few days. But I'm really not getting why there being a .blend that test just about every thing like this in one go hasn't been some we have for each blender release that would fix things like this from getting missed in optimizations.

There was a issue reported recently of the Principled BSDF reflecting more light than it theoretically should in the specular part of the material when the material base colour was above a certain threshold. This might of been what you were experiencing? If so, it has already been reported and it is not considered a "bug". Apparently this is because the Principled BSDF is based on a shader from a white paper from Disney. And the shader proposed by Disney has this exact same issue. Cycles replicates this issue to ensure compatibility between other software using the same shader model (which also most likely have that issue).

Still it would seem like it should have a checkmark to toggle weather or not it dose that.