Incorrect logic for negative evals on wrong input

[javjodar]

Acknowledgements

• I have searched (https://github.com/utmstack/UTMStack/issues) for past instances of this issue
• I have verified that my UTMStack version is up-to-date

Describe the bug

Regression Issue

• Select this option if this issue appears to be a regression.

Expected Behavior

Skip rule match on wrong input

Current Behavior

On negative rule, wrong input always matches rule

Reproduction Steps

Incorrect pattern in "not regexp" operator or "not in cidr"

Possible Solution

No response

Additional Information/Context

No response

UTMStack Version

10.5.19

Operating System and version

Hypervisor and Version | Server Vendor and Model

Browser and version